Qiskit benchmark
Timed against 7 other simulators
Qiskit 2.5.1 finished 121 of the 175 workloads it was run on and was the fastest of the 8 simulators in 0. At the median it took 22.3× the time of the fastest simulator in the same workload. What it is and how to install it is in its own documentation.
By circuit family
Where it is fast and where it is not
| Circuit family | Workloads finished | Fastest in | Median time against the fastest |
|---|---|---|---|
| Workloads finished 10 of 16 | Fastest in 0 | Median time against the fastest 20.6× | |
| Workloads finished 18 of 24 | Fastest in 0 | Median time against the fastest 33.7× | |
| Workloads finished 21 of 27 | Fastest in 0 | Median time against the fastest 18.7× | |
| Workloads finished 10 of 16 | Fastest in 0 | Median time against the fastest 27.8× | |
| Workloads finished 18 of 24 | Fastest in 0 | Median time against the fastest 24.1× | |
| Workloads finished 8 of 12 | Fastest in 0 | Median time against the fastest 12.0× | |
| Workloads finished 14 of 19 | Fastest in 0 | Median time against the fastest 25.0× | |
| Workloads finished 10 of 16 | Fastest in 0 | Median time against the fastest 22.8× | |
| Workloads finished 12 of 21 | Fastest in 0 | Median time against the fastest 7.8× |
Qiskit against each other simulator
On the workloads both finished
| Comparison | Workloads both finished | Qiskit faster in | The other faster in | Faster at the median |
|---|---|---|---|---|
| Workloads both finished 119 | Qiskit faster in 69 | The other faster in 50 | Faster at the median Qiskit 1.7× | |
| Workloads both finished 121 | Qiskit faster in 28 | The other faster in 93 | Faster at the median PennyLane Lightning 1.7× | |
| Workloads both finished 121 | Qiskit faster in 2 | The other faster in 119 | Faster at the median Qiskit Aer 1.7× | |
| Workloads both finished 109 | Qiskit faster in 35 | The other faster in 74 | Faster at the median Qiskit Aer (MPS) 1.1× | |
| Workloads both finished 121 | Qiskit faster in 31 | The other faster in 90 | Faster at the median Google qsim 1.4× | |
| Workloads both finished 121 | Qiskit faster in 0 | The other faster in 121 | Faster at the median Qulacs 6.6× | |
| Workloads both finished 104 | Qiskit faster in 0 | The other faster in 104 | Faster at the median TensorCircuit 5.6× |
Where it produced no timing
The status the benchmark recorded
A simulator that did not finish a workload keeps the status the benchmark recorded for it, and is left out of that workload's ranking.
| Recorded status | Operation | Workloads |
|---|---|---|
unsupported | Operation Gradient | Workloads 37 |
skip | Operation Expectation value | Workloads 17 |
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.