Benchmark insights

CPU vs GPU for pricing and risk in 2026

The fastest CPU against the fastest GPU on each workload, one GPU against a whole two-socket CPU server, all 6 platforms measured the same way, each with code tuned for it.

Throughput at the ranked size, 5 November 2026 round; higher is faster. Bars compare within each workload. CPUs in ochre, GPUs in blue; a second chip of the same kind is lighter.

Fastest of each

WorkloadFastest CPUFastest GPUGPU against CPU
Swaption portfolio, LMMAMD EPYC Turin, 44.0M/sAMD Instinct MI355X, 192M/s4.4×
Barrier options, Monte CarloAMD EPYC Turin, 1.04M/sAMD Instinct MI355X, 2.71M/s2.6×
American options, binomial latticeAMD EPYC Turin, 4.94M/sAMD Instinct MI355X, 7.26M/s1.5×
European options, Black-Scholes formulaIntel Xeon 6 (Granite Rapids), 23.2B/sAMD Instinct MI355X, 68.6B/s3.0×

On the LMM swaption portfolio the fastest GPU (AMD Instinct MI355X) is 4.4× faster than the fastest CPU (AMD EPYC Turin); on barrier options (Monte Carlo) the fastest GPU (AMD Instinct MI355X) is 2.6× faster than the fastest CPU (AMD EPYC Turin); on American options (binomial lattice) the fastest GPU (AMD Instinct MI355X) is 1.5× faster than the fastest CPU (AMD EPYC Turin); on European options (Black-Scholes formula) the fastest GPU (AMD Instinct MI355X) is 3.0× faster than the fastest CPU (Intel Xeon 6 (Granite Rapids)).

The hardware

AMD EPYC Turin
CPU · 2024 · AMD EPYC 9005 (Turin), 2 sockets
Cores
2 × 96
Threads
192
Memory
375 GiB
Peak power (measured)
320 W per socket
AMD Instinct MI355X
GPU · 2025
Cores
256 (CU)
Clock
2,400 MHz
Measured FP64 FMA ceiling, GFLOP/s
71,000
Memory bandwidth
8,000 GB/s
Memory
288 GB (maker figure)
Power limit
1,400 W
Intel Xeon 6 (Granite Rapids)
CPU · 2024 · Intel Xeon 6 P-core (Granite Rapids), 2 sockets
Cores
2 × 96
Threads
192
Memory
755 GiB
Power limit
600 W per socket

Energy per result

Energy is compared GPU with GPU and CPU with CPU, not between the two: GPUs read the board sensor alone, host excluded; CPUs the processor package alone, memory excluded. Each figure is on the results and in its measurement record.

No single ratio sizes a grid: the gap depends on the workload, so measure the ones that make up the bill.

How these were measured

Each platform ran code tuned for that chip under the same rules, in double precision: five launches per measurement, the middle three averaged, warm calls in every launch until the 95% confidence interval of their mean was within ±1% or until the call limit. Any test spreading more than 5% is repeated on a second machine of the same type, and the steadier of the two is published. A Black-Scholes call makes 100 passes over the whole batch, each counted as work, so its options per second are options × 100 passes over the time of a call. At every problem size, the option price is validated against the reference implementation's before any time counts. The full method is on How we measure.

More benchmark insights

All benchmark insights Current results