Papers › Stressing Out Modern Quantum Hardware: Performance Evaluation and Execution Insights
Stressing Out Modern Quantum Hardware: Performance Evaluation and Execution Insights
Aliza U. Siddiqui, Kaitlin Gili, Chris Ballance
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
Quantum hardware is progressing at a rapid pace and, alongside this progression, it is vital to challenge the capabilities of these machines using functionally complex algorithms. Doing so provides direct insights into the current capabilities of modern quantum hardware and where its breaking points lie. Stress testing is a technique used to evaluate a system by giving it a computational load beyond its specified thresholds and identifying the capacity under which it fails. We conduct a qualitative and quantitative evaluation of the Quantinuum H1 ion trap device using a stress test based protocol. Specifically, we utilize the quantum machine learning algorithm, the Quantum Neuron Born Machine, as the computationally intensive load for the device. Then, we linearly scale the number of repeat-until-success subroutines within the algorithm to determine the load under which the hardware fails and where the failure occurred within the quantum stack. Using this proposed method, we assess the hardware capacity to manage a computationally intensive QML algorithm and evaluate the hardware performance as the functional complexity of the algorithm is scaled. Alongside the quantitative performance results, we provide a qualitative discussion and resource estimation based on the insights obtained from conducting the stress test with the QNBM.
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections