Skip to content
aiqbench takeQuantum Computing

aiqbench analysis

This study provides a critical hardware-aware benchmarking map for near-term quantum control, revealing how cache limits and latency overheads dominate performance in small Hilbert spaces rather than raw arithmetic speed. By contrasting x86 CPUs, NVIDIA GPUs, and deterministic FPGAs, the authors demonstrate that optimization strategies like GRAPE must account for propagator build costs which can exceed propagation time at larger scales. These findings offer essential guidance for researchers selecting hardware architectures to minimize bottlenecks in real-time quantum control loops.
Source coveringarXiv
What this isA model's reading of the article and related coverage, written for aiqbench. Not the publisher's words.

Hardware-Aware Performance Characterization of Small Dense Lindblad Propagation for Near-Term Quantum Control

arXiv3 min read

arXiv:2603.18052v2 Announce Type: replace Abstract: Dense Lindblad propagation at the Hilbert-space sizes of near-term transmon control ($d = 3$, $9$, $27$) sits in a regime where cache boundaries, launch overhead, and fixed latency decide which hardware is useful, not peak arithmetic rate. This paper characterizes that regime on two x86 CPUs, two NVIDIA GPUs, and a low-cost FPGA. Each implementation is stated as an algorithm in $d$ with an idealized cost built from separately measured ceilings, and the measured gaps are attributed to specific mechanisms: thread fork/join, the strided read of the propagator, PCI Express (PCIe) transfers, and propagator re-upload. An end-to-end gradient-ascent (GRAPE-style) benchmark against released QuTiP 5.2.3 shows that fast propagation does not imply fast control optimization: the C path wins by up to two orders of magnitude at $d = 3$ but loses at $d = 27$, where the dense LU solve inside the Pad\'e propagator build takes over $90\%$ of the cost. The FPGA contributes a deterministic-latency operating point, $95$ cycles per step at a stress-characterized $108$ MHz with zero cycle spread over $1000$ trials, and its Q1.15 fixed-point drift is measured on the device. The results are a map of operating regimes for the measured grid, with the propagator build, not propagation, as the dominant cost at the largest size.

Abstract:Dense Lindblad propagation at the Hilbert-space sizes of near-term transmon control ($d = 3$, $9$, $27$) sits in a regime where cache boundaries, launch overhead, and fixed latency decide which hardware is useful, not peak arithmetic rate. This paper characterizes that regime on two x86 CPUs, two NVIDIA GPUs, and a low-cost FPGA. Each implementation is stated as an algorithm in $d$ with an idealized cost built from separately measured ceilings, and the measured gaps are attributed to specific mechanisms: thread fork/join, the strided read of the propagator, PCI Express (PCIe) transfers, and propagator re-upload. An end-to-end gradient-ascent (GRAPE-style) benchmark against released QuTiP 5.2.3 shows that fast propagation does not imply fast control optimization: the C path wins by up to two orders of magnitude at $d = 3$ but loses at $d = 27$, where the dense LU solve inside the Padé propagator build takes over $90\%$ of the cost. The FPGA contributes a deterministic-latency operating point, $95$ cycles per step at a stress-characterized $108$ MHz with zero cycle spread over $1000$ trials, and its Q1.15 fixed-point drift is measured on the device. The results are a map of operating regimes for the measured grid, with the propagator build, not propagation, as the dominant cost at the largest size.

14 pages, 6 figures, 12 tables, 5 algorithms. Under review at Journal of Computational Physics

arXiv:2603.18052 [quant-ph]

(or arXiv:2603.18052v2 [quant-ph] for this version)

https://doi.org/10.48550/arXiv.2603.18052 Focus to learn more arXiv-issued DOI via DataCite

arXivLabs is a framework that allows collaborators to develop and share new arXiv features directly on our website.

Both individuals and organizations that work with arXivLabs have embraced and accepted our values of openness, community, excellence, and user data privacy. arXiv is committed to these values and only works with partners that adhere to them.

Have an idea for a project that will add value for arXiv's community? Learn more about arXivLabs.

Full text under the publisher's open licence · 314 words

Related coverage