Sandbox CPU Burst Benchmark Stealth
Extra CPU capacity available when a workload exceeds its provisioned CPU allocation.
Provider leaderboard
31 published scores · Sandbox CPU Burst
- 1
88.35Weekly score
- 2
84.04Weekly score
- 3
82.16Weekly score
- 4
73.77Weekly score
- 5
73.20Weekly score
- 6
70.89Weekly score
- 7
68.94Weekly score
- 8
67.03Weekly score
- 9
66.66Weekly score
- 10
66.30Weekly score
- 11
65.94Weekly score
- 12
65.90Weekly score
- 13
65.72Weekly score
- 14
64.31Weekly score
- 15
62.96Weekly score
- 16
62.85Weekly score
- 17
62.16Weekly score
- 18
62.04Weekly score
- 19
61.98Weekly score
- 20
61.76Weekly score
- 21
61.49Weekly score
- 22
60.87Weekly score
- 23
59.98Weekly score
- 24
59.89Weekly score
- 25Uno33.99Weekly score
- 26
Pre-release23.40Weekly score
- 27
0.00Weekly score
- 27
0.00Weekly score
- 27
0.00Weekly score
- 27
0.00Weekly score
- 27
Pre-release0.00Weekly score
- —
No published score
- —
No published score
A missing score is unranked, not zero. Select a provider to see its scorecard.
Weekly score comparison
All 33 providers · score, not milliseconds
Methodology
What this benchmark measures
Extra CPU capacity available when a workload exceeds its provisioned CPU allocation.
How weekly scores are calculated
Each provider’s score is the average of this benchmark’s daily scores over the previous seven complete days. Days without scores are skipped, not counted as zero. A published zero remains a score; a missing value is unranked.
How rankings work
Providers are ranked by their published weekly score in the benchmark’s scoring direction. Equal scores share a rank, and the next rank skips the tied places. Only providers with published scores count toward the ranked field.
This page uses only the published weekly summary. It does not expose raw timings, daily runs or private logs.
Read the weekly scoring methodology