Spartan Server Labs

Sample results

This is what a Spartan Server Labs engagement produces: measured results for every BIOS profile, application benchmarks at increasing load, and an interactive dashboard.

Everything on this page is synthetic. The figures come from a fictional demonstration server called DEMO-SRV and do not describe any real server, customer or product. No serial numbers, licence details, host names or network addresses appear in these samples. In a real engagement, your own identifiers stay in your report and are never published.

1. Sample test results

Each profile is tested at 25, 50, 75 and 100% load, with power measured at every step, then run through a burn-in. The table compares three profiles on the same demonstration server.

BIOS profileCPU (blocks/s)Memory (GB/s)Disk (MB/s)System power at full CPU load (W)CPU blocks/s per wattBurn-in
Power Efficient326.824.01,9002151.52PASS, 4 h, max 72.9 °C
Low Latency380.029.01,9002751.38PASS, 4 h, max 74.0 °C
HPC425.633.01,9003081.38PASS, 4 h, max 75.0 °C

Network, GPU and DPU tests were skipped in this sample because the demonstration server has none of those devices. A real report says plainly what was and was not tested.

Power draw rises with load

010020030040025%50%75%100%CPU load levelSystem power (W)Power EfficientLow LatencyHPC

Work done at each load level

010020030040050025%50%75%100%CPU load levelCPU work (blocks/s)Power EfficientLow LatencyHPC

In this sample the HPC profile does the most work but draws the most power, while Power Efficient does the least work for the least power. The right choice depends on your workload, which is exactly what the comparison is for.

2. Sample application benchmark

Application workloads are run at increasing numbers of concurrent connections, to show where throughput peaks, where latency starts to climb and how much power each result costs. This sample shows a database benchmark (pgbench), then a summary of four workload types.

Database throughput against connections

01,0002,0003,0004,0005,0006,0001005001,0002,0005,000Concurrent database connectionsTransactions per secondPower EfficientLow LatencyHPC

Tail latency (99th percentile)

Connectionsp99 latency, Power Efficientp99 latency, Low Latencyp99 latency, HPC
1008.0 ms8.0 ms8.0 ms
50037.1 ms33.0 ms30.3 ms
1,000124.3 ms108.0 ms97.3 ms
2,000269.6 ms233.0 ms208.9 ms
5,0001,868.5 ms1,608.0 ms1,436.6 ms

Summary of four workload types

WorkloadToolBIOS profilePeak throughputHighest stable levelPower at peakThroughput per watt
DatabasepgbenchPower Efficient3,870 transactions/s2,000215 W18.0
Low Latency4,500 transactions/s2,000275 W16.4
HPC5,040 transactions/s2,000308 W16.4
Web servingHTTP loadPower Efficient22,360 requests/s5,000215 W104.0
Low Latency26,000 requests/s5,000275 W94.5
HPC29,120 requests/s5,000308 W94.5
Storagefio random readPower Efficient206,400 IOPS256215 W960.0
Low Latency240,000 IOPS256275 W872.7
HPC268,800 IOPS256308 W872.7
AI inferencePyTorch MLPPower Efficient38,700 samples/s1,024215 W180.0
Low Latency45,000 samples/s1,024275 W163.6
HPC50,400 samples/s1,024308 W163.6

Application workload tests are a new extension offered after a pilot, as described on the Services page. The tools shown are examples; we can run your own benchmark command instead.

3. Sample dashboard

The interactive dashboard works offline and lets you explore every result: inventory, power, performance, burn-in and application benchmarks, by profile. Try the tabs below, or open it full screen.

Synthetic data from the fictional server DEMO-SRV. The dashboard runs entirely in your browser. It makes no network requests and sends nothing anywhere.

Not sure which profile your servers should run?

Tell us about your servers. We will explain how a pilot would work, what it would take, and what you would receive.

Request a pilot