The most ordinary work one computer can do

[ Front page ] [ The edge ] [ Finished ] [ About ] [ Links ]

1,660 times the reference machine

Held by Lenovo ThinkSystem SR950 V3. Set 2026-06-29, and has stood for 120 days. Written down here 2026-10-03.

Two numbers on this page measure how fast a computer is and they do not agree about which computer that is. The other one is a warehouse of cabinets solving one enormous system of linear equations, which is arithmetic so regular that the machine knows where the next number is long before it needs it. This one is a single server running fourteen ordinary programs - a chess engine, CPython, GCC, LLVM, a compression library, a database, a network simulator, a simulator of a processor - compiled from source and run as many concurrent copies as the tester chooses, measured on how much it gets through rather than on how quickly it finishes any one of them. That is the code almost all computing actually consists of, and the order it puts machines in is not the order on the arithmetic lists. The figure is a ratio, not a count of anything: the publisher's formula is the number of copies multiplied by the reference machine's time divided by this machine's time, averaged across the fourteen programs, and the reference machine is a historical thirty-two-core Ampere eMAG box from 2019. So the record means roughly that many times as much of this work per unit of time as that one machine running a single copy. Two cautions belong on the number rather than under it. A throughput score rewards size, because the tester picks how many copies to run and the holder is an eight-socket machine with four hundred and eighty cores; the publisher keeps a separate speed metric for the different question of how fast one program finishes. And the suite is replaced every few years, with no conversion between generations, so this frontier can only ever be as old as the current suite. The institution behind it is older than this website's costume: SPEC was founded in 1988 by hardware and software vendors who had got tired of each other quoting benchmarks they had written themselves, and the method has not changed since - run the same programs everywhere, divide by a fixed reference machine, publish the configuration with the result. Only the programs and the reference machine get replaced. One of the fourteen is Stockfish, which is also the program holding another number on this page.

That description was written when this frontier was opened, on 2026-10-03, and is never rewritten. Where it and the number above it disagree, the number is the reading and the description is history.

What counts

The largest figure in the Base column of SPEC's list of all published SPECrate 2026 Integer results - the metric the publisher calls SPECrate2026_int_base. Base rather than Peak, and the choice decides the reading rather than decorating it: SPEC's rules require a base figure on every reported result and make peak optional, so the peak column is empty on a third of the list and empty on the row that holds this record, which means a maximum taken over peak would report a smaller number belonging to a different machine. Base is also the stricter build: every module of a language must be compiled with the same flags in the same order, where peak lets a tester tune each program separately. The list is ordered by test sponsor and carries no ranking of its own, so the reading is taken by sorting the whole column, and the row count is reconciled against the number of result documents the page links. Figures from SPEC CPU 2017 are a different measurement and are never read here: the publisher has retired that suite and states that no formula converts between the two.

What moves it

A tester publishes a higher base figure on SPECrate 2026 Integer and SPEC posts the result. Results are posted as vendors submit them rather than to a conference calendar, so this can move in any week.

Where to check it: https://www.spec.org/cpu2026/results/rint2026/

Last checked: 2026-10-25. The source itself last measured this: 2026-09-24.

Previous: Programs rebuilt without seeing the code   Next: The most questions ever answered against a hundred terabytes of data

[ Front page ] [ The edge ] [ Finished ] [ About ] [ Links ]