toomanymike

Many useful patches are posted to the upstream pass mailing list. They're rarely responded to. I don't know if that specifically drove the creation of this fork, but it's absolutely a frustration as a pass user

I've seen CPU throttling occur when limits aren't exhausted even on 5.4 kernels, so I don't believe the underlying kernel bug is fixed.

One option not mentioned in the post is to enable k8s' static CPU scheduler policy. With this option in place workloads in the "guaranteed" quality of service class that are allocated an integer CPU limit will be given exclusive use of their CPUs. I've found this also avoids the CFS bugs and eliminates CPU throttling, without removing CPU limits.

One thing to keep in mind is that this bug mostly impacts workloads that spin up more threads then they have allocated CPUs. For golang workloads you can set GOMAXPROCS to be equal to your CPU allocation and eliminate most throttling that way too, without messing with limits or the static scheduler policy

Super helpful, thanks!

Anyone have pointers to interesting companies in the climate tech space? Or tips for finding them?

Highlights include the ability to delete a topic, and Kafka-based consumer offset management.

There's a captcha