GHG: tune the CPU request for SSIM workshop #6309
Merged
Conversation
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
We tested spinning up multiple pods for the SSIM workshop. It always created a node per pod because the CPU availability was insufficient. I'm decreasing the CPU request here a bit to test if that helps put 2 user pods in a single node for the workshop. Changing the option for the non-workshop environment too just to help us test without being part of the workshop group.
|
Merging this PR will trigger the following deployment actions. Support deploymentsNo support upgrades will be triggered Staging deployments
Production deployments
|
3 tasks
|
cc @aprilmj we may need a bit of a timely look at this to get this in before the workshop starts next Tuesday. Currently, only one instance is being placed per node and wasting a lot of capacity - this should ideally fix that and fit two instances per node. |
yuvipanda
added a commit
to yuvipanda/pilot-hubs
that referenced
this pull request
Jul 2, 2025
In 2i2c-org#6309, we discovered that some of our resource allocations were now outdated. This adds a 2% wiggle room that should help with that
|
#6313 is the right fix but we can deploy this as is for now |
|
🎉🎉🎉🎉 Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/16035338108 |
yuvipanda
added a commit
to yuvipanda/pilot-hubs
that referenced
this pull request
Jul 15, 2025
In 2i2c-org#6309, we discovered that some of our resource allocations were now outdated. This adds a 2% wiggle room that should help with that
jnywong
pushed a commit
to jnywong/infrastructure
that referenced
this pull request
Aug 7, 2025
In 2i2c-org#6309, we discovered that some of our resource allocations were now outdated. This adds a 2% wiggle room that should help with that
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
We tested spinning up multiple pods for the SSIM workshop. It always created a node per pod because the CPU availability was insufficient.
I'm decreasing the CPU request here a bit to test if that helps put 2 user pods in a single node for the workshop.
Changing the option for the non-workshop environment too just to help us test without being part of the workshop group.
refs #6308