Quantum simulators compared

The same circuits, one host

8 simulators were timed on the same 175 workloads: 9 circuit families at 4 to 24 qubits, as expectation values, gradients and statevectors. A simulator is the fastest in a workload when it finished with the shortest time and the right answer.

Every simulator

Fastest in how many workloads

SimulatorVersionWorkloads finishedFastest inMedian time against the fastest
Version
0.45.1
Workloads finished
147 of 175
Fastest in
0
Median time against the fastest
32.3×
Version
0.45.0
Workloads finished
166 of 175
Fastest in
4
Median time against the fastest
7.2×
Version
2.5.1
Workloads finished
121 of 175
Fastest in
0
Median time against the fastest
22.3×
Version
–
Workloads finished
138 of 175
Fastest in
0
Median time against the fastest
10.2×
Version
–
Workloads finished
120 of 175
Fastest in
18
Median time against the fastest
17.0×
Version
–
Workloads finished
138 of 175
Fastest in
44
Median time against the fastest
4.0×
Version
0.6.14
Workloads finished
175 of 175
Fastest in
70
Median time against the fastest
1.7×
Version
1.8.0
Workloads finished
151 of 175
Fastest in
39
Median time against the fastest
2.2×

Head to head

Every pair, on the workloads both finished

How this was measured

One host, one harness

Every simulator ran the same circuits on one host, single-threaded and core-pinned, driven through one common harness, so any overhead the harness adds is charged to the simulator. Each result was checked against a reference implementation: a simulator that ran fast but returned the wrong answer is left out of the ranking. Nothing is interpolated or rescaled. A time was measured, or it is not shown.

Run 2026-08-10, 8 cores, threads=1. numpy 2.4.6, scipy 1.18.0, torch 2.13.0, numba 0.66.0, pennylane 0.45.1, pennylane_lightning 0.45.0, qiskit 2.5.1, qulacs 0.6.14, tensorcircuit 1.8.0, cudaq 0.15.1. One host and one thread make the comparison reproducible. It is not a prediction for your laptop.

The interactive tool shows the same measurements for any workload you pick, with the quantum hardware that could run it and what a run would cost.

Hardware figures each carry the source they came from and the date they were measured. The oldest in this set is 626 days old. Costs are bands, not quotes.

Host: Linux-6.8.0-1051-aws-x86_64-with-glibc2.35, 8 cores, threads=1, core-pinned. numpy 2.4.6, scipy 1.18.0, torch 2.13.0, numba 0.66.0, pennylane 0.45.1, pennylane_lightning 0.45.0. Every simulator was driven through one common harness, so any harness binding overhead is charged to the simulator rather than hidden.

© 2026 EigenOrbit. All rights reserved.