Benchmark Coverage
Spare Cores continuously inspects cloud servers and runs standardized benchmark workloads to measure performance and cost efficiency. Some instances cannot currently be inspected or benchmarked. This may happen when servers are temporarily unavailable (e.g. out of stock), not yet generally available (e.g. no pricing information available), restricted by vendor or account quotas (e.g. we cannot access larger GPU boxes on cloud credits), or affected by technical limitations such as API rate limits. The summary below shows benchmark coverage by cloud vendor:
VENDOR | IDENTIFIED SERVERS | INACTIVE SERVERS | ACTIVE SERVERS | EVALUATED ACTIVE SERVERS | MISSING ACTIVE SERVERS | ||||
|---|---|---|---|---|---|---|---|---|---|
Alibaba Cloud | 1885 | 1186 | 62.92% | 699 | 37.08% | 6 | 0.86% | 693 | 99.14% |
Amazon Web Services | 1194 | 15 | 1.26% | 1179 | 98.74% | 1144 | 97.03% | 35 | 2.97% |
Microsoft Azure | 1416 | 65 | 4.59% | 1351 | 95.41% | 907 | 67.14% | 444 | 32.86% |
Google Cloud Platform | 534 | 194 | 36.33% | 340 | 63.67% | 339 | 99.71% | 1 | 0.29% |
Hetzner Cloud | 34 | 9 | 26.47% | 25 | 73.53% | 25 | 100.00% | 0 | 0.00% |
OVHcloud | 103 | 35 | 33.98% | 68 | 66.02% | 64 | 94.12% | 4 | 5.88% |
UpCloud | 93 | 1 | 1.08% | 92 | 98.92% | 91 | 98.91% | 1 | 1.09% |
The table below provides detailed status and benchmark coverage for all discovered cloud servers, including pricing availability, hardware inspection results, and high-level benchmark workload status. You can filter the dataset by vendor, status, and specific benchmark families, along with free-text search. By default, the table is filtered for active instances with pricing information. When a specific benchmark is missing, you can click on the x icon to view the raw logs and metadata collected while we tried to run the benchmark. Note that the target page might return a 404 error if we were unable to start the server at all.