You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many jupyterhub's setup by 2i2c were initially setup to start dedicated nodes for users, this has several drawbacks that we can avoid by scheduling multiple users to run on individual nodes.
Drawbacks of dedicated nodes
inefficient use of cpu/memory paid for
increases cost
increases required cloud quota to request to scale to support X users
increased average startup times (server startup, image download)
Rationale & value to our mission
expected reduced cloud cost for communities
faster startup times on average
it becomes easier to handle events
Definition of completion and success
All communities use node sharing, even if options aren't presented like in many educational hubs.
Action points
Overview all communities still setup to provide user dedicated nodes
consideRatio
changed the title
Proto-goal: transition clusters only providing users with dedicated nodes transition to shared nodes
Transition clusters providing users with dedicated nodes to use shared nodes
Oct 11, 2023
Brief description
Many jupyterhub's setup by 2i2c were initially setup to start dedicated nodes for users, this has several drawbacks that we can avoid by scheduling multiple users to run on individual nodes.
Drawbacks of dedicated nodes
Rationale & value to our mission
Definition of completion and success
All communities use node sharing, even if options aren't presented like in many educational hubs.
Action points
Related
The text was updated successfully, but these errors were encountered: