reduce max workers to not surpass AWS vCPU limits #8
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.
Rich messaged me to let me know there’s a quota on how many vCPUs we can spin up at a time in the AWS account that nebari-workshop is running on. I did a little experimentation to estimate a resource usage for a class of 30, and we were going to be way over our allocation limit (assuming all the students are running dask calculations at the exact same time, which they probably will be). I had to bump your max number of workers down to 15 in all of your notebooks to put estimated usage within the range of what we have allocated. I tested out your notebooks and the longest dask calculations (in the standard suite and dscore notebooks) take ~3 mins to run with 15 workers.
Rich put in a request for a higher limit of vCPUs, but it is unlikely to be granted before the workshop. We can leave this as a draft on the off chance they do grant our request before the workshop and don't need to merge. But most likely you will want to merge this PR right before your workshop. Let's be in touch when it gets close to showtime.
To avoid any issues in the class, I would recommend that you really emphasize that students shut down their clusters each time you get to that point in a notebook. I would also recommend that instructors who are watching others present (and not presenting themselves) consider not running the notebooks themselves, just to reduce the usage of resources. (Though based on my estimation, the instructors shouldn't push us over the limit - just wanting to be on the safe side if possible)