Strongly-entangling ansatz: which simulator is fastest

RX/RY/RZ layers with a CNOT ring

8 simulators ran this circuit at 4 to 24 qubits, 16 workloads in all. Qulacs was the fastest in 6, TensorCircuit in 4, Google qsim in 4 and Qiskit Aer (MPS) in 2. The tables below hold every time as it was measured, with the fastest in each row marked. Open this circuit in the interactive tool to see the hardware that could run it and what a run would cost.

Expectation value, local observable, depth 3

Time per run, by qubit count

QubitsPennyLanePennyLane LightningQiskitQiskit AerQiskit Aer (MPS)Google qsimQulacsTensorCircuit
4 qubits
PennyLane
4.02 ms
PennyLane Lightning
2.43 ms
Qiskit
1.96 ms
Qiskit Aer
1.60 ms
Qiskit Aer (MPS)
1.83 ms
Google qsim
2.87 ms
Qulacs
68.2 µs
TensorCircuit
224 µs
8 qubits
PennyLane
7.98 ms
PennyLane Lightning
4.09 ms
Qiskit
4.37 ms
Qiskit Aer
2.79 ms
Qiskit Aer (MPS)
4.02 ms
Google qsim
5.35 ms
Qulacs
177 µs
TensorCircuit
418 µs
12 qubits
PennyLane
14.3 ms
PennyLane Lightning
5.88 ms
Qiskit
9.48 ms
Qiskit Aer
6.03 ms
Qiskit Aer (MPS)
18.2 ms
Google qsim
7.79 ms
Qulacs
1.56 ms
TensorCircuit
1.46 ms
16 qubits
PennyLane
70.1 ms
PennyLane Lightning
13.1 ms
Qiskit
101 ms
Qiskit Aer
32.4 ms
Qiskit Aer (MPS)
57.7 ms
Google qsim
11.4 ms
Qulacs
30.0 ms
TensorCircuit
20.7 ms
20 qubits
PennyLane
1.67 s
PennyLane Lightning
177 ms
Qiskit
2.61 s
Qiskit Aer
551 ms
Qiskit Aer (MPS)
92.3 ms
Google qsim
41.6 ms
Qulacs
595 ms
TensorCircuit
467 ms
24 qubits
PennyLane
skip
PennyLane Lightning
6.45 s
Qiskit
skip
Qiskit Aer
10.8 s
Qiskit Aer (MPS)
131 ms
Google qsim
1.05 s
Qulacs
13.2 s
TensorCircuit
13.0 s

Expectation value, global observable (all_z), depth 3

Time per run, by qubit count

QubitsPennyLanePennyLane LightningQiskitQiskit AerQiskit Aer (MPS)Google qsimQulacsTensorCircuit
4 qubits
PennyLane
4.44 ms
PennyLane Lightning
2.65 ms
Qiskit
2.09 ms
Qiskit Aer
1.66 ms
Qiskit Aer (MPS)
1.93 ms
Google qsim
2.98 ms
Qulacs
77.7 µs
TensorCircuit
229 µs
8 qubits
PennyLane
8.95 ms
PennyLane Lightning
4.38 ms
Qiskit
4.65 ms
Qiskit Aer
2.94 ms
Qiskit Aer (MPS)
4.52 ms
Google qsim
5.57 ms
Qulacs
222 µs
TensorCircuit
458 µs
12 qubits
PennyLane
16.0 ms
PennyLane Lightning
6.44 ms
Qiskit
9.75 ms
Qiskit Aer
6.63 ms
Qiskit Aer (MPS)
32.6 ms
Google qsim
8.01 ms
Qulacs
2.50 ms
TensorCircuit
2.01 ms
16 qubits
PennyLane
78.2 ms
PennyLane Lightning
17.1 ms
Qiskit
96.2 ms
Qiskit Aer
40.6 ms
Qiskit Aer (MPS)
164 ms
Google qsim
12.3 ms
Qulacs
50.6 ms
TensorCircuit
50.3 ms
20 qubits
PennyLane
2.73 s
PennyLane Lightning
290 ms
Qiskit
2.62 s
Qiskit Aer
697 ms
Qiskit Aer (MPS)
347 ms
Google qsim
59.3 ms
Qulacs
1.02 s
TensorCircuit
1.13 s
24 qubits
PennyLane
skip
PennyLane Lightning
12.3 s
Qiskit
skip
Qiskit Aer
13.7 s
Qiskit Aer (MPS)
560 ms
Google qsim
1.44 s
Qulacs
21.4 s
TensorCircuit
26.2 s

Gradient, local observable, depth 3

Time per run, by qubit count

QubitsPennyLanePennyLane LightningQiskitQiskit AerQiskit Aer (MPS)Google qsimQulacsTensorCircuit
4 qubits
PennyLane
29.0 ms
PennyLane Lightning
5.82 ms
Qiskit
unsupported
Qiskit Aer
unsupported
Qiskit Aer (MPS)
unsupported
Google qsim
unsupported
Qulacs
278 µs
TensorCircuit
395 µs
8 qubits
PennyLane
58.9 ms
PennyLane Lightning
9.62 ms
Qiskit
unsupported
Qiskit Aer
unsupported
Qiskit Aer (MPS)
unsupported
Google qsim
unsupported
Qulacs
822 µs
TensorCircuit
986 µs
12 qubits
PennyLane
125 ms
PennyLane Lightning
15.2 ms
Qiskit
unsupported
Qiskit Aer
unsupported
Qiskit Aer (MPS)
unsupported
Google qsim
unsupported
Qulacs
8.63 ms
TensorCircuit
4.28 ms
16 qubits
PennyLane
538 ms
PennyLane Lightning
77.4 ms
Qiskit
unsupported
Qiskit Aer
unsupported
Qiskit Aer (MPS)
unsupported
Google qsim
unsupported
Qulacs
180 ms
TensorCircuit
69.9 ms

Which quantum computers can run it

At depth 3, 1,000 shots

Quantum computerCan run it up toBorderline up toEstimated cost at that size
Can run it up to
16 qubits
Borderline up to
32 qubits
Estimated cost at that size
$200.30–$600.90
via AWS Braket
Can run it up to
32 qubits
Borderline up to
–
Estimated cost at that size
$200.30–$600.90
via AWS Braket
Can run it up to
8 qubits
Borderline up to
12 qubits
Estimated cost at that size
$23.80–$71.40
via AWS Braket
Can run it up to
96 qubits
Borderline up to
–
Estimated cost at that size
Not priced
this vendor publishes no rate card
Can run it up to
48 qubits
Borderline up to
–
Estimated cost at that size
Not priced
this vendor publishes no rate card
Can run it up to
48 qubits
Borderline up to
–
Estimated cost at that size
Not priced
this vendor publishes no rate card
Can run it up to
–
Borderline up to
–
Estimated cost at that size
–
Can run it up to
–
Borderline up to
–
Estimated cost at that size
–
Can run it up to
–
Borderline up to
–
Estimated cost at that size
–
Can run it up to
32 qubits
Borderline up to
96 qubits
Estimated cost at that size
from $0.015
via IBM Quantum. 0.01s at maximum throughput, so this is a floor
Can run it up to
48 qubits
Borderline up to
128 qubits
Estimated cost at that size
from $0.421
via IBM Quantum. 0.26s at maximum throughput, so this is a floor
Can run it up to
32 qubits
Borderline up to
96 qubits
Estimated cost at that size
from $0.421
via IBM Quantum. 0.26s at maximum throughput, so this is a floor
Can run it up to
4 qubits
Borderline up to
32 qubits
Estimated cost at that size
$0.725–$2.17
via AWS Braket
Can run it up to
24 qubits
Borderline up to
48 qubits
Estimated cost at that size
$1.90–$5.70
via AWS Braket
Can run it up to
16 qubits
Borderline up to
20 qubits
Estimated cost at that size
$1.75–$5.25
via AWS Braket

Sizes are the grid's own: 4, 8, 12, 16, 20, 24, 32, 48, 64, 96, 128, 156 qubits. A device can run a circuit when a clean run is more likely than not, and is borderline when it is better than one in fifty. The cost is for one run of 1,000 shots at the largest size in the row, as a band and not a quote.

The simulators

Each one across every circuit family

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.