Sources
15 entries in 3 parts
In the MCP server
cpuperf://section/15

Standard suites

  1. 01
    SPEC CPU 2026 Run and Reporting Rules manual

    Defines base against peak, rate against speed, the threading models a speed run may use and an Arm reference machine.

  2. 02
    SPEC CPU: The Next Generation paper

    Where the committee states how workloads were chosen and hardened, and defines the rolling round-robin rate.

  3. 03
    SPEC CPU2026: Characterization, Representativeness, and Cross-Suite Comparison paper

    Measures with counters what each workload stresses on x86 and Arm server parts, beside data-centre and inference suites.

  4. 04
    MLPerf Inference Rules repository

    Fixes model, accuracy floor and query pattern per scenario, so a Server score is throughput under a latency bound.

  5. 05
    DCPerf: An Open-Source, Battle-Tested Performance Benchmark Suite for Datacenter Workloads paper

    Shows standard suites misproject data-centre servers, and states the fleet-matching method the suite is built by.

Microbenchmark suites

  1. 01
    Memory Bandwidth and Machine Balance in Current High Performance Computers paper

    Defines sustainable bandwidth as what unit-stride loops get, not bus peak, and machine balance as flops per access.

  2. 02
    STREAM Benchmark Reference Information report

    Sets the array size rule, timing over repeated trials, and counting bytes a loop asks for, not what the cache moved.

  3. 03
    lmbench: Portable Tools for Performance Analysis paper

    Origin of the one-mechanism-per-test method for memory, system call, pipe and socket latency, and what each leaves out.

  4. 04
    uarch-bench repository

    Isolates memory-level parallelism from load latency as separate tests, with DVFS held off before timing, x86 Linux only.

  5. 05
    nanoBench: A Low-Overhead Tool for Running Microbenchmarks on x86 Systems paper

    Shows why kernel mode with interrupts off matters, removes harness overhead, then recovers cache replacement policies.

Reproduce it

triad bandwidth by thread count against the vendor figure.

Reproduce it · 15-stream-bandwidth Memory bandwidth by thread count and working set Vendor bandwidth is a package number; one thread and cache-resident data cannot reveal it

Methodology and what suites miss

  1. 01
    How Not to Lie with Statistics: The Correct Way to Summarize Benchmark Results paper

    Origin of the rule that normalised results take the geometric mean, which a SPEC ratio and the crimes list rest on.

  2. 02
    Systems Benchmarking Crimes report

    Checklist of evaluation faults from sub-setting and improper baselines to arithmetic means of ratios, each with a fix.

  3. 03
    Scientific Benchmarking of Parallel Computing Systems paper

    Sets which mean fits costs, rates and ratios, when confidence intervals are owed, and the absolute base a speedup needs.

  4. 04
    Rigorous Benchmarking in Reasonable Time paper

    Decides how many builds, runs and iterations an experiment needs by measuring at which level the variation arises.

  5. 05
    Profiling a warehouse-scale computer paper

    Fleet counter profile showing services stall on instruction fetch and burn cycles in shared routines, which SPEC lacks.