Post #2558609
2026-04-16 10:36 UTC
Granted, the node where I run klipper is a very shitty, dual-core machine. Easy to overwhelm.
How band roaming ends up causing clang to peg the CPU is, in hindsight, somewhat easy to see, but still fun nonetheless.
Replies (2)
-
@nadia@raru.re 2026-04-16 10:38
Now, how on earth do I fix this... Maybe I can uuuh give a static core to klipper so it runs entirely undisturbed? Some `renice` sidecar hack to give it realtime priority? Limit cilium container to 1 core? The latter is the easiest but also the most annoying for the rest of the nodes, who have more and more powerful cores and don't use wifi. :bunThinking:
-
@domi@donotsta.re 2026-04-16 11:37
@nadia@raru.re wait. what? why is BPF needed for this at all? roaming between wifi networks should take virtually zero CPU time, least you use a 30 year old machine that being said, your setup does sound horribly overcomplicated, so maybe I just don’t know better