SPEC CPU scores influence processor design, compiler work, and purchasing long after the suite’s applications become familiar. The 2026 revision addresses two gaps in CPU2017: too little behavioral diversity and a rate mode that largely runs copies of the same program[1].
More code and more parallel behavior
CPU2026 contains 52 component benchmarks, up from 43. It adds front-end-bound integer applications with large code footprints and expands multithreading: 13 floating-point and nine integer SPECspeed components use parallelism. Applications remain native C, C++, and Fortran so results avoid the run-to-run and portability complications of managed runtimes.
Rolling Round-Robin Rate (RRR) is the conceptual change. Each core executes all benchmarks in a roster, but starts at a different offset and advances through the list. The machine therefore sees mixed instruction, cache, memory, and branch behavior under one repeatable schedule. Researchers may use subsets and different increments, provided the configuration remains documented.
What we take from it
RRR standardizes workload construction, not the policy conclusion. The suite intentionally leaves researchers free to compute throughput, fairness, interference, or QoS metrics from raw results. That makes the method useful for heterogeneous core allocation and shared-cache studies without pretending one aggregate score answers every question. CPU2026 will still miss managed services and distributed applications, but it gives general-purpose microarchitecture a more modern and reproducible baseline.
Source and attribution
This article is an original editorial summary with a newly created figure. No paper text, figure, or table is reproduced. The authors made a public arXiv manuscript available; the authoritative ISCA proceedings version is © IEEE 2026.