Qulacs benchmark

Timed against 7 other simulators

Qulacs 0.6.14 finished 175 of the 175 workloads it was run on and was the fastest of the 8 simulators in 70. At the median it took 1.7× 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 familyWorkloads finishedFastest inMedian time against the fastest
Workloads finished
16 of 16
Fastest in
6
Median time against the fastest
2.8×
Workloads finished
24 of 24
Fastest in
7
Median time against the fastest
2.9×
Workloads finished
27 of 27
Fastest in
14
Median time against the fastest
1.0×
Workloads finished
16 of 16
Fastest in
9
Median time against the fastest
1.0×
Workloads finished
24 of 24
Fastest in
12
Median time against the fastest
1.1×
Workloads finished
12 of 12
Fastest in
4
Median time against the fastest
2.0×
Workloads finished
19 of 19
Fastest in
10
Median time against the fastest
1.0×
Workloads finished
16 of 16
Fastest in
6
Median time against the fastest
1.6×
Workloads finished
21 of 21
Fastest in
2
Median time against the fastest
4.6×

Qulacs against each other simulator

On the workloads both finished

ComparisonWorkloads both finishedQulacs faster inThe other faster inFaster at the median
Workloads both finished
147
Qulacs faster in
147
The other faster in
0
Faster at the median
Qulacs 10.6×
Workloads both finished
166
Qulacs faster in
95
The other faster in
71
Faster at the median
Qulacs 2.6×
Workloads both finished
121
Qulacs faster in
121
The other faster in
0
Faster at the median
Qulacs 6.6×
Workloads both finished
138
Qulacs faster in
102
The other faster in
36
Faster at the median
Qulacs 2.6×
Workloads both finished
120
Qulacs faster in
90
The other faster in
30
Faster at the median
Qulacs 14.1×
Workloads both finished
138
Qulacs faster in
74
The other faster in
64
Faster at the median
Qulacs 3.0×
Workloads both finished
151
Qulacs faster in
100
The other faster in
51
Faster at the median
Qulacs 1.3×

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.