Kai Krakow
Kai Krakow
Yeah okay I think I get how the numbers calculate. Thanks for the explanation.
Okay, so I thought I didn't see that behavior with last years LTS kernel and I observed bad memory pressure after going to 6.1. But coincidentally, your change to bees...
Following up from https://github.com/Zygo/bees/issues/268#issuecomment-2068025791: > ... find out why btrfs is causing that high memory fragmentation. I feel like this has become worse and worse with each LTS kernel version....
Is `BEES_MAX_EXTENT_REF_COUNT` and env var, or is it a defined constant in the source code?
> Lately I've been running with `vm.swappiness=0` and `BEES_MAX_EXTENT_REF_COUNT` set to `9999`. With those settings there's no swapping at all. I've created a patch (9999 max ref count) and reverted...
So for a multi-instance bees service, we should probably have one runtime directory per instance? OTOH, I wonder if that's intended behavior of systemd, or if it is a bug......
Does it work with `RuntimeDirectory=bees/%I`?
> It works better with `RuntimeDirectory=bees/%i`. `%I` will create nested directories as it replaces `-` with `/`. beesd still places files in `/run/bees` though, so these files are preserved. Oh...
Yeah, it should be completely fine running the hash file on non-btrfs filesystems. I'm running it the same way here - actually by NOT using the beesd wrapper. Maybe create...
If you are using customized configs (like a beeshome path differing from defaults), you should create a systemd override file instead to add the needed configs tp the service. You...