Skip to content

Use static CPU Manager for Core Pinning - #45

Merged
mamoutou-diarra merged 5 commits into
mainfrom
mamoutou/use_static_cpu_manager
Aug 6, 2026
Merged

mamoutou-diarra merged 5 commits into
mainfrom
mamoutou/use_static_cpu_manager

Conversation

@mamoutou-diarra

@mamoutou-diarra mamoutou-diarra commented Aug 2, 2026 •

Copy link
Copy Markdown
Collaborator

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

  • Set kubelet cpuManagerPolicy to static: guarantee pinning for guaranteed-qos class pods, the allocated core_id will never be allocated to another pod

Other Unrelated Changes

  • Update dst_dashboard backend image to v1.3 (new feature: avoid boxplot to cross yaxis upon zoom; add vaclab node resources and topology via prometheus)

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

@mamoutou-diarra mamoutou-diarra self-assigned this Aug 2, 2026
@mamoutou-diarra mamoutou-diarra added the ift IFT commitments label Aug 2, 2026
@mamoutou-diarra mamoutou-diarra linked an issue Aug 2, 2026 that may be closed by this pull request
@mamoutou-diarra mamoutou-diarra moved this to In review in DST Aug 2, 2026
@mamoutou-diarra
mamoutou-diarra merged commit c0f4c99 into main Aug 6, 2026
@github-project-automation github-project-automation Bot moved this from In review to Done in DST Aug 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ift IFT commitments

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Analyze current stack (recurring)

2 participants