PennyLane Lightning benchmark
Timed against 7 other simulators
PennyLane Lightning 0.45.0 finished 166 of the 175 workloads it was run on and was the fastest of the 8 simulators in 4. At the median it took 7.2× 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 16 of 16 | Fastest in 0 | Median time against the fastest 22.4× | |
| Workloads finished 24 of 24 | Fastest in 0 | Median time against the fastest 12.9× | |
| Workloads finished 27 of 27 | Fastest in 1 | Median time against the fastest 5.2× | |
| Workloads finished 16 of 16 | Fastest in 1 | Median time against the fastest 5.5× | |
| Workloads finished 24 of 24 | Fastest in 1 | Median time against the fastest 5.2× | |
| Workloads finished 12 of 12 | Fastest in 0 | Median time against the fastest 3.2× | |
| Workloads finished 19 of 19 | Fastest in 1 | Median time against the fastest 6.9× | |
| Workloads finished 16 of 16 | Fastest in 0 | Median time against the fastest 8.3× | |
| Workloads finished 12 of 21 | Fastest in 0 | Median time against the fastest 1.7× |
PennyLane Lightning against each other simulator
On the workloads both finished
| Comparison | Workloads both finished | PennyLane Lightning faster in | The other faster in | Faster at the median |
|---|---|---|---|---|
| Workloads both finished 147 | PennyLane Lightning faster in 141 | The other faster in 6 | Faster at the median PennyLane Lightning 3.4× | |
| Workloads both finished 121 | PennyLane Lightning faster in 93 | The other faster in 28 | Faster at the median PennyLane Lightning 1.7× | |
| Workloads both finished 138 | PennyLane Lightning faster in 74 | The other faster in 64 | Faster at the median PennyLane Lightning 1.1× | |
| Workloads both finished 120 | PennyLane Lightning faster in 54 | The other faster in 66 | Faster at the median Qiskit Aer (MPS) 1.1× | |
| Workloads both finished 138 | PennyLane Lightning faster in 31 | The other faster in 107 | Faster at the median Google qsim 1.2× | |
| Workloads both finished 166 | PennyLane Lightning faster in 71 | The other faster in 95 | Faster at the median Qulacs 2.6× | |
| Workloads both finished 142 | PennyLane Lightning faster in 51 | The other faster in 91 | Faster at the median TensorCircuit 3.4× |
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 9 |
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.