Vladimir Smirnov

Hm, I'm absolutely unfamiliar with shaders, but if there is a way to test performance, I can try with both M1 and M2 devices. However I can try only if...

I've tried to actually compile version from commit around the time when you've implemented mesh shaders (b301f95afd7c4dfa8303921bc0f44896ffe4c32e to be precise), but it was not working correctly if I uncomment that...

Thanks. I've tried to run it with mesh shader enabled and indeed I haven't noticed any problems anymore, but in terms of performance... well... It's about 4x slower than without...

In the same scene on M2 Max I get 32-45 FPS, so that's much better than before, but still far from ~120 without Mesh.

You can limit amount of updates that it can do, or you can use cgroups to slowdown disk writes.

> Memory usage stayed at 0.2% (viewed through top, rhel8 OS). Well... percents are not very helpful without knowing how much RAM you have :) Also, it depends on the...

My .02: if you are traversing symlinks you need to some way to workaround endless loops as well.

> so I assume it is production ready (https://github.com/go-graphite/go-carbon/issues/35) by now. Is this correct? go-carbon initially was created by @lomik to replace carbon-cache at the place where he worked back...

And about tagging support - after I finished my reply I've remembered that it is not entierly correct. go-carbon supports tags on write-path so you can feed it tagged metrics...

``` vsmirnov@ml905507 ~/go/gopath_third_party/src/github.com/lomik/go-whisper $ OK=0; ERR=0; while :; do go test; if [[ $? -ne 0 ]]; then ERR=$((ERR+1)); else OK=$((OK+1)); fi; if [[ $ERR -gt 10 ]]; then break;...