-
Notifications
You must be signed in to change notification settings - Fork 17
Add startup times documentation #281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
user/faq.md
Outdated
|
|
||
| ## The user server can fit on a node/machine that already exists and has enough resources available to serve it. | ||
| 1. If it can't fit or such a node doesn't exits, then the autoscaler will trigger the creation of a new node. | ||
| This can take up from a couple of minutes, to even 10 min or more. When the 10 minutes cap is hit, the server creation will throw a `TimeoutError` and you'll have to re-trigger the server creation process so you'll be assigned to the newly created node. Although not impossible, this is not common and we don't see it happing that often. In practice, we've noticed higher node startup times, with larger machines, like the ones with GPUs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| This can take up from a couple of minutes, to even 10 min or more. When the 10 minutes cap is hit, the server creation will throw a `TimeoutError` and you'll have to re-trigger the server creation process so you'll be assigned to the newly created node. Although not impossible, this is not common and we don't see it happing that often. In practice, we've noticed higher node startup times, with larger machines, like the ones with GPUs. | |
| This can take from a couple of minutes, to even 10 min or more. When the 10 minutes cap is hit, the server creation will throw a `TimeoutError` and you'll have to re-trigger the server creation process so you'll be assigned to the newly created node. Although not impossible, this is not common and we don't see it happing that often. In practice, we've noticed higher node startup times, with larger machines, like the ones with GPUs. |
user/index.md
Outdated
|
|
||
| :::: | ||
|
|
||
| :::{grid-item-card} Frequently Asked Questions? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| :::{grid-item-card} Frequently Asked Questions? | |
| :::{grid-item-card} Frequently Asked Questions |
|
Nice! I think we need to overhaul our docs more generally, so I'm in favour of these going here for now! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great, thanks so much @GeorgianaElena for being proactive and documenting this!
I've pushed a couple of changes and will merge:
- Streamlined the text a bit just to shrink it down and make it more bullet-y
- Added this to a new
basics/topic folder - Made this page specifically about startup times - we can always re-integrate this into a single FAQ if we want in the future!
- Added some cross references
|
Thanks for making this better @choldgraf and @agoose77 💟 |
As part of 2i2c-org/infrastructure#7042, I thought I could revive #150 instead of burying the answer in Freshdesk.
I didn't know where should it go, so I figured a FAQ would be a good home for it where we can gather other questions like this.
Fixes #150