Repository navigation
ci: require perf=fast nodes for Gradle and kaniko build pods (#559) - #569
Merged
Merged
Conversation
The perf=slow nodes (conway00-05) run at 1.5 GHz versus 2.4 GHz on the perf=fast ones (conway06-10). Once the 4Gi request let heavy pods fit on the 8 GB nodes, the scheduler started placing both Gradle pods of a build there despite the preferred perf=fast affinity, and the larger test suite then ran past the 30-minute build limit. Make perf=fast a required node affinity for heavy (Gradle/kaniko) pods; light pods keep the soft preference. With the existing one-heavy-pod-per- node anti-affinity this allows up to five heavy pods at once and queues the rest. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
The perf=slow nodes (conway00-05) run at 1.5 GHz versus 2.4 GHz on the perf=fast ones (conway06-10). Once the 4Gi request let heavy pods fit on the 8 GB nodes, the scheduler started placing both Gradle pods of a build there despite the preferred perf=fast affinity, and the larger test suite then ran past the 30-minute build limit.
Make perf=fast a required node affinity for heavy (Gradle/kaniko) pods; light pods keep the soft preference. With the existing one-heavy-pod-per- node anti-affinity this allows up to five heavy pods at once and queues the rest.