4 ms·
Do you offer some sort of keep_warm parameter that removes this latency (for a greater cost)?
by andes314 3y ago
Do you offer some sort of keep_warm parameter that removes this latency (for a greater cost)?
- mrkurt 3y agoYou control machine lifecycles. To scale down, you just set the appropriate restart policy, then exit(0). You can also opt to let our proxy stop machines for you, but the most granular option is to just do it in code. So yes, kind of. You just wait before you exit.
- Aeolun 3y agoSo just to confirm, for these workloads, it’d start a machine when the request comes in, and then shut it down immediately after the request is finished (with some 30-60s in between I suppose)? Is there some way to keep it up if additional requests are in the queue? Edit: Found my answer elsewhere (yes).