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
Now I would like to deploy on CDMS (after #48), the main issue is that scaling up is very slow, it takes about 20 min to get another node up.
So to maximize savings we could just keep the master running which supports 1 user (with 5 GB memory), a second concurrent user trying to connect will have to wait 20 min for their session to start
We keep master + 1 node always running, so only after those are full (or someone asks for a full node) we trigger autoscaling
@pibion what do you think? We could also try a couple of weeks with 1 and then decide.
I would like to set this up only after the redeploy (#48), so there is lots of time to discuss this.
The text was updated successfully, but these errors were encountered:
Autoscaling support for our deployment from the official project is still very far away, see zonca#34
So I implemented a hacked-up script myself, see https://zonca.dev/2021/01/autoscaling_script_kubespray_jupyterhub.html, I tested on a sample deployment and worked just fine.
Now I would like to deploy on CDMS (after #48), the main issue is that scaling up is very slow, it takes about 20 min to get another node up.
master
running which supports 1 user (with 5 GB memory), a second concurrent user trying to connect will have to wait 20 min for their session to start@pibion what do you think? We could also try a couple of weeks with 1 and then decide.
I would like to set this up only after the redeploy (#48), so there is lots of time to discuss this.
The text was updated successfully, but these errors were encountered: