Allocate half of a CPU per user session #201
Merged
Conversation
This file contains 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
This value was changed, as the puppet nodes are being taken out of service and so, there will be a higher number of user sessions running in the SWAN kubernetes cluster. Therefore, taking into account the maximum number of CPUs available, it was decided to request half of a CPU per user session, to allow for more user sessions to be scheduled. This level of overcommiting is fine, under the assumption most users will be idle for the majority of the time and will only require more CPU resources when executing notebook cells.
PMax5
force-pushed
the
feature/cpu-limit
branch
from
b963389 to
8878d10
Compare
etejedor
approved these changes
Jan 17, 2024
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.
This value was changed, as the puppet nodes are being taken out of service and so, there will be a higher number of user sessions running in the SWAN kubernetes cluster.
Therefore, taking into account the maximum number of CPUs available, it was decided to allocate half of a CPU per user session, to allow for more user sessions to be scheduled.