Use static CPU Manager for Core Pinning - #45
Merged
Merged
Conversation
AlbertoSoutullo
approved these changes
Aug 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
RLN proof generation takes long time in the vaclab cluster because of the CPU frequency and the way kubernetes allocates cores to pods in non-dedicated manner: a core allocated to a pod is also used by other pods and by the system, this is particularly harmful for single-threaded apps, since they'll be constantly preempted and need to fight for cpu cycles.
Changes
Other Unrelated Changes
Note
The static cpuManager is live only on the metal-01 node for now, I'll do it on all the nodes after a couple of days of observation