Repository navigation
Pack parallel catchup v2 workers 3 per node - #447
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jayz22
approved these changes
Oct 19, 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.
Bumps the worker spread
maxSkewfrom 2 to 3 so Karpenter packs 3 workers per node instead of 2.maxSkewworkers. At 2, 1024 workers need 512 nodes.catchupnodepool's 3072 cpu limit capped it. stellar/kube#5513 added fallback pools with their own limits, so build 1963 went to 512 nodes: $239/hr and $732 for catchup vs ~$635 on 384 nodes.Testing (ssc-test, prod's catchup pools mirrored, 60 pods with the worker's requests and spread rule):
maxSkew: 2: 30 nodes, 2 per nodemaxSkew: 3: 20 nodes, 3 per node, 84% memory requestedhelm templaterendersmaxSkew: 3on every worker pod🤖 Generated with Claude Code