What is burst capacity?
Burst capacity is how many environments a provider actually delivers when many are requested at once, which is often very different from its advertised latency for one.
The gap is measurable, and it moves. In an independent test requesting 100 concurrent sandboxes, one provider went from serving 12 to serving all 100 within two weeks. Both runs are real, which is the point: one good day tells you nothing about the next one.
For batch work this is the reliability number that matters. A fan-out that half-completes invalidates an evaluation rather than degrading it, because the environments that did not start are not a random sample.
Related
This is one of the terms in the Promigence glossary.
Run your own workload on it, free
Send a repo and the command you run against it, whatever that is: an eval suite, an RL rollout, a CI job, a queue of coding tasks. We build the environment once, run it a thousand times, and send back the timings, the failures and an exact price. Free, once, on your real workload.
- 1,000 runs of your own command, on your own repo
- What each one cost in wall clock, and anything that failed
- Whether a failure was your code or the environment
- An exact price for your real volume
Not ready to hand over a repo? Read the quickstart or check the numbers first.