Abstract
Quantum computing in the NISQ era requires advanced emulation tools to facilitate the development and validation of complex quantum algorithms, as current quantum devices remain too noisy and resource-limited. This work presents a comprehensive review of quantum emulation software available for HPC centers using various comparison metrics to evaluate parallelization, precision, acceleration via Graphics Processing Unit (GPU), emulation with noise, among others. The comparative analysis evaluates four quantum emulation frameworks (QuEST, Qaptiva HPC, CUDA-Q, and PennyLane) across three hardware platforms with distinct characteristics: two HPC clusters (Spartan-Eviden and Joliot-Curie TGCC) and one quantum emulation appliance (Eviden Qaptiva 804). The scope of this analysis is fundamentally tied to the state-vector emulation paradigm. The experimental results of our evaluation reveal that performance depends on classical hardware configuration and circuit characteristics, that is, CUDA-Q excels in single-GPU environments, while Qaptiva HPC shows advantages in distributed multi-node configurations (both CPU and GPU).
Keywords
1. Introduction
High-performance computing (HPC) systems represent the cutting edge of today’s computing power, combining thousands of interconnected processors to solve highly complex scientific and engineering problems. These supercomputers have been instrumental in significant advances in fields such as climate simulation, drug design, materials research, and modeling of complex physical phenomena. 1
However, there are certain computationally intensive problems that, due to their exponential nature, are intractable for even the most advanced HPC systems. This is where quantum computing emerges as a promising complementary technology, leveraging quantum mechanical principles such as superposition and entanglement to address these challenges. 2
Quantum computing is attracting interest for its potential to address exponentially complex tasks in diverse fields such as cryptography, 3 chemistry, 4 combinatorial optimization problems, 5 finance, 6 medicine, 7 meteorology, 8 and defense. 9 Despite these achievements, current quantum computers, which have tens to hundreds of physical qubits, remain in the Noisy Intermediate-Scale Quantum (NISQ) era, due to which quantum computing faces important challenges, such as the limited number of qubits, topological constraints, reduced connectivity, and high noise and error rates. These scalability and fidelity barriers of quantum systems have motivated intense research in hardware and software, with the goal of overcoming these limitations and moving into the era of large-scale error-correcting quantum computing.10,11
To overcome the limitations of NISQ systems, HPC centers are incorporating quantum emulation environments that leverage their High-Performance Infrastructure. These emulators, available through different vendors and solutions on the market, such as Qaptiva (Eviden), 12 Qiskit (IBM), 13 Quantum Simulator (Intel) 14 or Cirq (Google), 15 allow emulating the behavior of quantum circuits using classical computing resources. The integration of these emulators into HPC ecosystems enables the exploration of quantum algorithms that would otherwise be impossible on either quantum processing units (QPUs) or classical emulators.
In this context, parallel and distributed emulators have emerged as key tools, as they enable the infrastructure of HPC clusters to be leveraged through efficient partitioning of computational loads. This approach not only enables the emulation of quantum circuits at a larger scale and complexity, but also significantly reduces execution times, facilitating hybrid quantum-classical workflows to solve large-scale scientific and industrial problems. 16 However, quantum emulation capabilities in HPC remain limited by the available classical resources, especially in terms of memory.
Therefore, it is necessary to look for quantum emulation software that optimizes the utilization of HPC system resources. This software must be capable of being deployed on any HPC cluster regardless of technology, as well as enabling multi-core, multi-node, and GPU-level parallelization, thus providing the ability to distribute quantum emulation workloads and allowing more complex and deeper circuits to be addressed while reducing execution times.
In this study, we compared the four quantum emulation frameworks for HPC clusters, including experimentally evaluated benchmarking on three different platforms: two HPC systems, one CPU-only and one GPU-accelerated, and a quantum emulation appliance. This article is structured as follows: Background section explains how quantum emulators work and their fundamentals, including a comparative table of quantum emulation software for HPC; Description of Quantum Emulators section presents a technical summary of the four emulators under test, describing their architectures, parallelization capabilities, and performance optimizations; Qaptiva HPC Workflow section provides a detailed methodology of Qaptiva HPC, which is the quantum emulator introduced in this work, while Results section presents the results obtained for three evaluation platforms. Finally, Conclusions and future work section discusses the conclusions and proposes lines of future work in this area.
2. Background
Currently, many companies and research groups are investing in integrating quantum computing with HPC to develop SLURM-managed heterogeneous architectures that combine Central Processing Units (CPUs), GPUs, and QPUs. These technologies are designed to optimize complex workloads and provide more efficient solutions for industry.
In this heterogeneous ecosystem, quantum processing capabilities can be accessed either through physical QPUs (implemented using superconducting, 17 trapped-ion 18 or photonic 19 technologies) or through quantum emulators, which reproduce the functional behavior and instruction set of a QPU without offering quantum speedups. These emulators, when integrated with HPC infrastructures, can take advantage of the processing power of supercomputers to significantly expand their emulation capacity, allowing them to emulate circuits with a higher number of qubits and greater depth. Also the HPC infrastructures can leverage these emulators to integrate quantum capabilities to their computations without counting on a quantum computer.
2.1. HPC quantum emulators
Several companies in the field have developed emulators capable of mimicking the behavior of quantum computers while leveraging the power of classical computing. Table 1 compares the capabilities of various emulator package providers, focusing on features that make them suitable for HPC. The comparison is structured into different categories, including the numerical precision at which the emulator operates, support for CPU (multi-node or multi-core) and GPU parallelism, GPU compatibility for accelerated computation, noise emulation, job scheduling integration, limitation on the number of qubits that can be emulated, availability of technical support, and overall evaluation across heterogeneous HPC architectures when supported by the underlying runtime.
Comparison of state-of-the-art quantum emulators compatible with HPC clusters.
GPU parallelism indicates support for distributed GPU execution across multiple nodes, often implemented using MPI with CUDA-aware communication or libraries like NCCL.
Is a tensor networks emulator.
Uses PyCOMPSs for CPU and GPU parallelism.
It supports GPU acceleration if a cuQuantum appliance is used.
Uses PGAS for CPU and GPU parallelism.
Qubit count corresponds to photonic qubits.
The table summarizes different features of several HPC emulators. Notation: (–) indicates that no information was provided by the developers for that feature; (⊙ ) denotes emulators that offer technical support via GitHub; (†) indicates emulators that do not fragment circuits across GPU nodes, instead they replicate the full circuit on each node and run a single shot, which limits scalability and is only suitable for noiseless emulation; and (*) denotes those based on the OpenCL programming framework.
Regarding the emulator capabilities, thanks to HPC systems, most packages can emulate circuits with more than 35 qubits, with some, like QuEST, reaching up to
Since we are in the NISQ era, although on the path to the transition to the Intermediate-Scale Quantum (ISQ) era, 67 support for noise modeling is an important feature and it is provided by nearly all vendors listed in Table 1. Another key aspect to consider is the numerical precision at which the emulator operates, typically offering either single or double precision. Single precision is particularly relevant when aiming to balance memory usage with output accuracy, allowing users to tradeoff between emulation cost and fidelity. Some emulation software, such as Qaptiva, uses double precision by default but allows switching to single precision when improved computational efficiency is prioritized over fidelity.
One of the most important characteristics that emulator software must include is the possibility of parallelizing different parts of the computation across different cores of the CPU, a technique known as multi-threading. OpenMP is an Application Programming Interface (API) that simplifies the development of parallel applications by providing a high-level, flexible model for multi-threading in shared-memory systems. Naturally, all the software emulators included in Table 1 are compatible with OpenMP or a similar API. Another desirable feature for emulators integrated into HPC clusters is compatibility with multi-node parallelism, where each node has its own CPU and memory. This parallelization is typically achieved through Message Passing Interface (MPI), a standard programming interface for coordinating and sharing information efficiently across distributed systems. Emulators like Qaptiva, 23 PennyLane Lightning, 65 and QuEST 63 support MPI, whereas others, such as Qibo, 42 lag behind in this regard.
In addition to CPU-based parallelization techniques, GPU acceleration has become increasingly important. Graphic Processing Units provide an advantage due to their high memory bandwidth and parallel architecture, particularly well-suited for the linear algebra operations of quantum algorithms. The main two GPU providers on the market are NVIDIA and AMD and while many emulators are compatible with NVIDIA GPUs, only a few support AMD devices, including Qaptiva, qsim-Cirq 28 and SV-Sim. 38 Apart from single-node GPU acceleration, some vendors (Eviden, Xanadu, Nvidia, and others) also support distributed GPU computing, where different GPU nodes communicate via MPI. This feature is particularly appropriate for noisy emulations of a large number of qubits. 68
Schedulers play a key role in managing computing resources and coordinating job execution in HPC clusters. However, limitations often arise not from the scheduler itself, but from the lack of integration between the emulator and the cluster’s scheduling system. When such integration is absent or insufficient, flexibility is reduced and execution may be delayed. In contrast, emulators that offer built-in support for schedulers (e.g., SLURM or HTCondor) or enable straightforward integration with the HPC environment facilitate easier deployment, better resource utilization, and more efficient scaling across multiple nodes or GPUs.
The support service is especially important in this field due to the complexity of integrating HPC and quantum computing. Only a few vendors studied here offer customized support services to assist users in debugging and implementing their solutions, which can be a key factor for researchers and developers working with advanced emulations. Most of the emulators included in this study are open source, which often means they lack dedicated technical support. This can result in significant overhead in debugging and maintenance efforts.
Having reviewed the different characteristics shown in Table 1, we can conclude that the emulators with the most complete feature set are Qaptiva HPC (Eviden), Qiskit Aer (IBM), SV-Sim (PNNL), QuEST (Univ. of Oxford), and PennyLane Lightning (Xanadu). These five emulators offer all considered technical features, although only Qaptiva HPC and Qiskit Aer supplement these with personalized technical support. Other emulators often fall short in areas such as multi-node parallelism, scheduler integration, or GPU acceleration. In addition, six providers do not offer configurable precision between single and double modes.
Table 1 summarizes the state-of-the-art in HPC-oriented quantum emulators. However, not all listed tools meet the technical requirements for large-scale benchmarking on multi-node systems. For our experimental study, we selected the candidates and selected only those that (1) provide mature state-vector support above 30 qubits; (2) include multi-core, multi-GPU, or MPI-enabled backends; (3) are compatible with the hardware and software stack of our test platforms; and (4) ensure stable and reproducible execution. Based on these criteria, the emulators chosen for in-depth evaluation are Qaptiva HPC (Eviden), QuEST (Univ. of Oxford), PennyLane Lightning (Xanadu), and CUDA-Q.
3. Description of quantum emulators
This section presents a technical description of the four quantum emulators for HPC used in this study. Their architectures, parallelization capabilities, performance optimizations, and specific implementation characteristics are summarized, providing a solid foundation for understanding the differences and similarities between the platforms. Note that since Qaptiva is being introduced in this paper, a more detailed section will be included. The other emulators, such as QuEST, 63 PennyLane, 65 and CUDA-Q, 37 have already been discussed in previous works. Therefore, only a brief description of these emulators will be provided here. For more comprehensive information, we refer readers to the original sources.
3.1. QuEST HPC emulator
QuEST is a high-performance quantum emulator developed by the University of Oxford and is designed specifically for the accurate emulation of quantum circuits in distributed and parallel systems. QuEST’s architecture is based on advanced parallelization techniques that enable the efficient use of available computational resources. The emulator uses OpenMP for multi-core parallelization, allowing the computational load to be distributed efficiently across multiple CPU cores. For distributed systems, QuEST implements MPI, facilitating communication between nodes and enabling the emulation of quantum circuits that require computational resources exceeding the capabilities of a single node. This hybrid parallelization architecture allows QuEST to scale from desktop systems to massive HPC clusters, adapting to the specific computational needs of each application. 63
The performance optimizations implemented in QuEST are fundamental to its ability to handle large-scale quantum circuits. The emulator uses Single Instruction Multiple Data (SIMD) instructions to vectorize operations, significantly accelerating quantum data processing. 63
QuEST can run seamlessly under standard HPC schedulers (SLURM, PBS, LSF) because its MPI-based model is fully compatible with HPC batch systems, although it does not provide explicit scheduler integration.
The QuEST programming interface is designed to provide both performance and ease of use. The native C/C++ API allows granular control over quantum operations and maximizes computational performance. To facilitate development and integration with existing workflows, QuEST provides Python bindings through PyQuEST, allowing researchers to leverage the emulator’s capabilities from more accessible programming environments.
3.2. CUDA-Q
CUDA-Q is an open-source platform developed by NVIDIA for accelerated quantum computing, with specific capabilities for HPC environments. 69 It is designed to facilitate the integration of quantum and classical resources, enabling the orchestration of hybrid applications that combine QPUs, GPUs, and CPUs in a distributed HPC infrastructure. 69
The cuQuantum SDK consists of two main components: cuStateVec and cuTensorNet, which cover the needs of state-vector and tensor network based emulators, respectively. 37
The multi-GPU and multi-node capabilities of cuQuantum SDK allow quantum emulations to be scaled across multiple devices and nodes, with multi-node state as tensor network slicing and intermediate caching, to optimize performance in distributed emulations on HPC clusters. 37
The cuTensorNet component includes approximate emulation methods based on the MPS, Projected Entangled Pair State (PEPS), and other factored tensor representations optimized for execution on HPC infrastructures. 37 By leveraging the power of NVIDIA’s latest GPU architectures, quantum circuit emulators that have adopted cuQuantum SDK demonstrate significant speedup compared to CPU-only execution. 37 CuQuantum has been used to demonstrate large-scale emulations in HPC environments, such as a tensor network-based emulation of the Quantum Approximate Optimization Algorithm (QAOA) MaxCut problem. 37
CUDA-Q includes specialized libraries such as CUDA-Q QEC for quantum error correction and CUDA-Q Solvers with optimized implementations of hybrid algorithms, such as Variational Quantum Eigensolver (VQE) and QAOA. 69 The capabilities provided by cuQuantum SDK are available through programming interfaces in both Python and C, facilitating its use in existing HPC workflows. 37 The framework is available as a Python package through PyPI, and its source code is available on GitHub. 70
CUDA-Q’s native integration with distributed GPU infrastructures, its ability to scale quantum emulations across multiple devices and nodes using cuQuantum SDK, and its use of HPC-optimized primitives makes it a suitable choice for applications requiring large-scale quantum emulations in supercomputing environments.37,69
3.3. PennyLane
PennyLane is an open-source framework developed by Xanadu for programming quantum circuits and quantum computing. 71 It provides tools for building, optimizing, and running quantum circuits, with an emphasis on integration with classical machine learning frameworks, such as PyTorch, TensorFlow, and JAX, enabling automatic quantum circuit differentiation for quantum machine learning applications.
The framework is designed to facilitate the development of hybrid quantum-classical algorithms through its plugin architecture, which allows the connection of quantum circuits with different quantum hardware emulators and backends. PennyLane supports multiple quantum devices, including state-vector emulators, matrix-density emulators, and hardware from different vendors, providing flexibility in selecting the execution backend according to the requirements of each application. 71
Regarding HPC capabilities, PennyLane Lightning has an ecosystem of plugins that enables emulation on HPC systems: 65 (a) a state-vector emulator written in C++ with optional additions of OpenMP and gate-level parallelized SIMD kernels; (b) lightning.gpu, a state-vector emulator based on the NVIDIA cuQuantum SDK that implements a distributed state-vector emulator based on MPI; and (c) lightning.kokkos, a state-vector emulator written with Kokkos that can exploit the inherent parallelism of modern processing units by supporting OpenMP, CUDA, or Heterogeneous-computing Interface for Portability (HIP) programming models, and also offers distributed state-vector emulation via MPI; (d) lightning.tensor, a tensor network emulator based on the NVIDIA cuQuantum SDK that supports methods such as the Matrix Product State (MPS) and exact tensor network.
PennyLane lightning implements optimizations to improve CPU performance through intrinsic SIMD and multi-threading and supports task-based batch execution across multiple GPUs. 65 Furthermore, it enables the distributed execution of quantum circuits (forward and gradient-based) across multiple nodes, facilitating the scaling of quantum emulations in HPC infrastructures. 65 The reported benchmarks for PennyLane lightning show emulation capabilities that can reach up to 30 qubits on a single device or node and up to 41 qubits using multiple distributed nodes. 65
Performance comparisons with other high-performance emulator packages show performance advantages for certain configurations and architectures. 65 The framework offers a Python API that abstracts the implementation details of different backends, allowing code to be written to run on different quantum emulators or devices without modification. This portability facilitates the comparison of results between different emulation platforms and quantum hardware as well as the migration of experiments between different computational environments, including distributed HPC infrastructures.65,71
3.4. Qaptiva HPC
Qaptiva HPC is a software solution that provides several state of the art quantum emulators to run in HPC environments. It is designed to be compatible with standard HPC clusters and seamlessly integrates with schedulers like SLURM, streamlining the creation, scheduling, and execution of quantum jobs.
Qaptiva HPC uses advanced optimization and algorithm techniques designed to maximize emulation performance. These techniques include qubit routing, which minimizes inter-node communications by efficiently managing swap gates and gate rewriting, which reduces the complexity of the initial circuit. These optimizations, applied transparently to the user, significantly reduce communication and memory overhead in distributed executions, often leading to substantial improvements in emulation time and memory efficiency compared with conventional distributed state-vector emulators.
The software is versatile, supporting any type of quantum gate, if the corresponding matrix can be stored in a node. In addition, it supports different types of measurements, such as “sampling” and “observable,” extending its applications in different scenarios. However, as is typical of quantum computing, qubit emulation presents an exponential growth: each additional qubit requires twice as many resources, in terms of memory.
The emulation capacity of Qaptiva HPC is limited by the available memory in the cluster, which is defined by the number of nodes and the amount of RAM on each node. The maximum number of qubits that could be emulated per node was calculated using Equation 1. It should be noted that this represents a theoretical limit, which may not always be attainable in practice owing to various factors, such as memory overhead from system operations, which can reduce the available qubits by approximately one compared to the theoretical calculation.
The parameter

Diagram of a circuit in Qaptiva HPC, showing local qubits located in the main node and remote qubits requiring MPI communication for inter-node operations.
The Qaptiva HPC architecture divides qubits into two types: local and remote, as illustrated in Figure 1. Local qubits are processed within a single node, which eliminates the need for inter-node communications and maximizes efficiency. Operations on remote qubits, on the other hand, require coordination between nodes via the MPI. For these cases, swap gates are introduced before and after operations involving remote qubits, which increases both communication and computation. This division, combined with the aforementioned optimization techniques, ensures an efficient balance between resource usage and emulation capability.
To illustrate the optimization of communications between local and remote qubits, consider the example described below: Figure 2(a) presents an initial circuit of five qubits without topological restrictions; subsequently in Figure 2(b), the Naive plugin 72 identifies the remote qubits (q3 and q4) and determines the need to incorporate seven SWAP gates to bring remote qubits into the same node where the operation must be applied; finally, Figure 2(c) shows the same circuit compiled with Qaptiva HPC, whose optimization process reduces these SWAP gates to only three, more efficiently preserving the interaction between local and remote qubits and mitigating the associated communication overhead.

SWAP gate optimization in Qaptiva HPC: (a) original circuit; (b) Naive compilation requiring 7 SWAPs; (c) optimized Qaptiva HPC compilation reducing them to 3.
Currently, Qaptiva HPC offers two types of quantum emulators: DLinAlg (ideal, noiseless emulation) and DNoisy (noisy emulation), both fully integrated with the SLURM resource scheduler and optimized for HPC clusters.
DLinAlg is an emulator based on linear algebra, designed to represent pure quantum states by state-vectors composed of complex amplitudes. These amplitudes can be stored in either single or double precision, depending on the user’s requirements. In the double-precision case, each floating-point complex amplitude occupies
On the other hand, DNoisy is an emulator specifically designed to emulate quantum circuits with noise. This emulator allows the user to incorporate imperfections of the quantum computer hardware during the simulation to predict the effects of noise. It supports both bitstring sampling and observable measurement, and is compatible with multinode configurations, making it particularly suitable for distributed environments. DNoisy has two different simulation methods: deterministic and stochastic noise simulation. The deterministic mode represents the system’s density matrix, allowing for precise noise modeling but limiting the number of qubits due to high memory consumption. In contrast, the stochastic mode utilizes a probability distribution over pure states, enabling the emulation of a larger number of qubits but requiring a significant number of samples to achieve reliable results. In this study, we focus on the deterministic mode.
While DLinAlg scales efficiently for pure states, the density-matrix representation in DNoisy requires a
4. Qaptiva HPC workflow
This section describes the procedure for performing distributed emulations on an HPC cluster using Qaptiva HPC, detailing the execution of both ideal quantum emulations and those incorporating noise models.
The job distribution process to the available nodes of the cluster, schematically depicted in Figure 3, begins when the user connects to the login node, where the SLURM batch script used to schedule the quantum emulation job is prepared. In this script, the user specifies the required computational resources such as the number of nodes, tasks per node, memory, and walltime along with the execution configuration. Once the script is ready, the job is submitted to the SLURM scheduler using the sbatch command, which manages the allocation of resources and the dispatch of the quantum jobs across the cluster.

Task distribution among the nodes of a cluster.
Once the job is submitted via sbatch, it is distributed to multiple nodes in the cluster. The main node manages the initial optimization of the job, which is especially relevant in variational algorithms, where parameters must be adjusted iteratively. In these cases, the optimization is performed at the main node before distributing the quantum circuits to the compute nodes, where the emulation is executed. Subsequently, the results are collected at the main node to continue the iterative optimization process. This centralized approach improves efficiency and facilitates workflow management by the user.
Below are examples of emulation, accompanied by a detailed explanation of each step in the process.
4.1. Procedure for DLinAlg emulations
To submit a job on a cluster in a SLURM environment, the following steps are followed:
Description of the quantum program in a Python script.
Writing SLURM batch submission script.
Submitting the SLURM batch script using the sbatch command.
Reading the quantum program’s output from the result file generated by the SLURM command.
4.1.1. Description of the quantum program
The first step is to prepare a Python script that describes the quantum program to be executed, as can be seen in Code 1. In this example, our aim is to emulate a distributed QAOA MaxCut circuit using DLinAlg. The algorithm will be executed on a simple graph with
QAOA Quantum Program.
DLinAlg can operate with or without SLURM. In a SLURM environment, DLinAlg can automatically deduce the default parameters from the SLURM sbatch parameters, such as the number of processes and threads used for emulation, provided that these are not explicitly specified. Outside a SLURM environment, the user must specify all MPI parameters explicitly (for example, the number of processes and threads) and execute the program manually using mpirun.
4.1.2. Writing the SLURM batch script
The next step is to define a SLURM batch script to configure the cluster’s resources. This script includes options preceded by
SLURM Batch Script.
In this example, the emulation will run on one node with one task per node and
4.1.3. Submitting the SLURM Job
The batch script is submitted to the cluster using the sbatch command, as shown in Code 3. In non-SLURM environments, the emulation is launched manually using mpirun, and all MPI parameters (number of processes and threads) must be specified by the user.
SLURM Batch Submit.
4.1.4. Reading Results
Once the job is completed, results can be retrieved from the SLURM output log (slurm-<jobid>.out) and any files generated by the Python program, as shown in Code 4.
Obtaining results.
4.2. Procedure for DNoisy emulations (Deterministic mode)
Once the execution of a quantum program in DLinAlg has been explained, we introduce DNoisy, a tool designed to integrate and manage noise models in quantum circuits. Its implementation, illustrated in Figure 4, combines emulation and optimization to enhance the accuracy of emulations of real quantum computer hardware as discussed in detail in paper: 73
Definition of the Initial Circuit and Noise Model: An initial quantum circuit is defined along with a noise model that characterizes the effects of a noisy environment. Both are provided as input to DNoisy, which applies the noise model to the circuit and generates a modified version, referred to as the noisy circuit.
Processing the Noisy Circuit: DNoisy processes the initial circuit alongside the noise model and produces a noisy circuit that incorporates environmental effects. The generated noisy circuit depends on the simulation method chosen: in the deterministic mode, the noisy circuit doubles the number of qubits in the original circuit to explicitly represent correlations and noise effects, while in the stochastic mode, the number of qubits in the original circuit is retained. On the other hand, ideal gates are replaced by noisy gates represented by quantum transformations called Kraus channels.
Emulation with DLinAlg: The noisy circuit is executed using DLinAlg, which processes the emulation and generates the corresponding results. In deterministic noise simulation method, the density matrix is vectorized to obtain an representation of a vector of size
This approach combines the capabilities of DNoisy and DLinAlg, providing an efficient solution for studying quantum circuits under noisy conditions. Its integration into HPC environments enables high fidelity emulations, optimizing the performance of emulations for quantum computing research. Below is an example of code, Code 5, illustrating the implementation of the QAOA algorithm with noise on an HPC cluster.

Diagram of the implementation of a deterministic noise model in Qaptiva HPC.
Noise Implementation.
5. Results
This section presents the results of a comparative analysis of the quantum emulators tested in this work. It is organized into three parts, each corresponding to one of the evaluation platforms used: Spartan-Eviden, Joliot-Curie 75 TGCC, and Qaptiva 804 76 Eviden.
The emulators evaluated in this study were initially identified from the state-of-the-art overview presented in Table 1. The inclusion criteria were (1) compatibility with HPC cluster environments, (2) support for state-vector emulation paradigm, (3) availability of parallelization capabilities (CPU and/or GPU), and (4) active technical support and documentation. The exclusion criteria eliminated emulators that (1) did not support HPC cluster deployment, (2) were limited to specific hardware architectures without cluster compatibility, or (3) lacked sufficient documentation for reproducible experiments. From the pool of emulators satisfying these requirements, we selected a representative subset for detailed benchmarking: QuEST, Qaptiva HPC, CUDA-Q, and PennyLane.
The experimental evaluation followed a structured methodology in four stages, as presented in Figure 5. This methodology includes (1) selection of the computing platform, (2) selection of the quantum emulator, (3) circuit execution, and (4) result analysis.

Experimental evaluation methodology.
For Spartan-Eviden, 74 the study evaluated scalability in relation to tests performed on different nodes, parallelization, and communications. For Joliot-Curie, 75 the analysis consisted of evaluating GPU usage through different configurations. Finally, for the quantum emulator, the study assessed how emulation times scale with the number of qubits and the depth of the circuits evaluated.
The complete experimental setup, including the evaluated emulators and circuits used on each platform, is summarized in Table 2. The characteristics of each platform as well as the detailed results of each comparative study are presented in this section.
Experimental setup: platforms, CPUs, GPUs, memory RAM, emulators and circuits evaluated.
On the one hand, for the HPC platforms, two types of circuits were evaluated: a QAOA MaxCut circuit with algorithmic depth
Random circuit and QAOA MaxCut for mono GPU emulation.
Random circuit and QAOA MaxCut for multi-node 4 GPU emulation.
On the other hand, for the Qaptiva 804 appliance, three circuits from the Munich Quantum Toolkit (MQT) Bench benchmark78,79 were selected, chosen for their relevance in HPC-oriented scenarios due to their scalability and algorithmic diversity: QAOA, QNN, and HHL. The characteristics of these circuits, including total gate count and depth, are summarized in Table 5.
CPU-only emulation performance of HHL, QNN and QAOA circuits on the Qaptiva 804 appliance.
To ensure strict comparability across emulators, the MQT Bench circuits,78,79 part of the MQT and designed for systematic evaluation of quantum software tools, were generated using backend-dependent native gates and the “Clifford + T + rotations” gate set.
All circuits were subsequently exported to OpenQASM 2.0 to guarantee reproducibility and consistent interpretation across platforms. Furthermore, all executions were performed using 1024 shots, with measurements applied to all qubits, ensuring uniform workloads and fully comparable timing results.
5.1. Spartan-Eviden
A comparative study was performed on Eviden’s Spartan cluster,
80
using the DLinAlg emulator configured with
Figure 6 shows the logarithmic scale emulation times for a QAOA circuit as a function of the number of qubits used. The DLinAlg emulator exhibits significantly lower times in all scenarios evaluated compared to QuEST, covering configurations from

Comparison of emulation times for a QAOA circuit versus the number of emulated qubits, using different nodes on the Spartan cluster. DLinAlg are shown with a solid line, while QuEST are shown with a dashed line.
Moreover, Figure 6 reveals that QuEST emulation times grow more rapidly—as an approximately exponential trend—compared to those of DLinAlg for all evaluated node configurations. It can also be observed that the emulation times of DLinAlg using a given number of nodes are comparable to those obtained by QuEST when using approximately twice as many nodes. For instance, the emulation curve corresponding to
These results indicate that DLinAlg provides better computational efficiency than QuEST under the tested conditions. The experimental results demonstrate a significant reduction in emulation times, with improvements of up to 59% in the best-case scenario using
In Figure 7, the core efficiency of the DLinAlg emulator, expressed in Giga Floating Point Operations Per Second (GFLOPS) per core, is analyzed as a function of the number of qubits emulated. The results indicate that DLinAlg maintains a relatively constant core efficiency on the Spartan cluster, ranging from

Comparison of core efficiency in DLinAlg, measured in GFLOPS per core, depending on the number of nodes and the number of emulated qubits on the Spartan cluster.
Overall, these results show that, across all evaluated benchmarks, DLinAlg attains a higher number of simulable qubits, exhibits greater scalability, and delivers lower execution times compared to QuEST. The optimization of resource management and the mitigation of bottlenecks related to inter-node communication position DLinAlg as a robust tool for large-scale quantum emulations on HPC clusters.
In Figure 8 the ratio between the communication time and compute time is evaluated as the number of nodes increases. The results show that as the number of nodes increases, the workload on each individual node decreases, whereas the communication between nodes increases. This explains why the ratio between the communication time and the computation time increases with the number of nodes. Furthermore, a slightly logarithmic growth trend can be observed up to approximately 60 nodes, after which the ratio increases in a more linear manner. This behavior reflects the inherent trade-off in distributed quantum emulations: reducing the individual node workload comes at the cost of increased inter-node communication overhead, highlighting the challenges faced by MPI-based emulators in optimizing communication in large-scale configurations.

Evolution of the ratio between the communication time to the compute time on the Spartan cluster.
Finally, Figure 9 presents the scalability results obtained exclusively with DLinAlg, using configurations from

Comparison of emulation times versus the number of emulated qubits on the Spartan cluster, for configurations ranging from 2 to 256 nodes, showing the impact of scalability on performance.
5.2. Joliot-Curie TGCC
The comparative analysis on GPUs was conducted on the V100 partition of the Joliot-Curie supercomputer. To ensure homogeneous execution conditions, all hyperthreads were enabled, and the MPI configuration used one process per GPU, resulting in four MPI processes per node when all GPUs were used.
Experiments were performed using three GPU-accelerated quantum emulators, CUDA-Q, Qaptiva HPC, and QuEST, executing both, single-node emulation with one GPU and distributed multi-node emulation with four GPUs.
5.2.1. A—Single-Node GPU emulation
The results summarized in Table 3 and illustrated in Figure 10 confirm the feasibility of full state-vector emulation of 29-qubit circuits on a single GPU.

Comparison of emulation times as a function of the number of emulated qubits (25 to 29 qubits) on a single node equipped with one GPU, for two distinct circuit types: QAOA and random circuits.
Across both evaluated circuits, CUDA-Q consistently emerged as the fastest emulator, followed by Qaptiva HPC and, finally, QuEST. As expected, execution times for the random circuit were substantially higher than for the QAOA circuit, a consequence of its markedly greater depth and a more than 500% increase in total gate count. This difference in structural complexity directly impacts emulation performance and is reflected consistently across all platforms.
In the 25–29 qubit range, CUDA-Q achieved an average speedup of approximately Õ2 over Qaptiva HPC and Õ5 over QuEST for the random circuit. For the QAOA circuit, the speedup was even more pronounced, reaching Õ3 and Õ20, respectively.
This behavior is clearly illustrated in Figure 10: CUDA-Q consistently exhibits the lowest execution times, followed by Qaptiva HPC and QuEST, for both types of circuits. The figure also highlights the sharper increase in execution time observed for the random circuit relative to the QAOA circuit across all emulators. This trend is directly attributable to the substantially greater depth of the random circuit, which amplifies computational complexity and accentuates performance differences between emulation backends.
5.2.2. B—Multi-node GPU emulation
During the multi-node tests, a limitation was identified in the CUDA-Q Docker container (version cu12-0.12.0) that prevented the use of GPU Direct Memory Copy (GDRCopy) for inter-node communication, necessitating its deactivation via the UCX_TLS environment variable for this specific backend. In contrast, QuEST results were obtained with GDRCopy enabled. Regarding Qaptiva HPC, although the software fully supports GDRCopy and yields higher performance when active, the results presented in this comparison were obtained with GDRCopy disabled. This configuration was chosen specifically to ensure a fair baseline comparison with the CUDA-Q environment.
Experiments were conducted using four GPUs (one full V100 node) for both circuits, and the results are summarized in Table 4.
Unlike the single-node scenario, Qaptiva HPC achieved better performance in multi-node configurations, particularly in cases where communication became more demanding. With eight nodes, Qaptiva HPC achieved an approximate speedup of Õ1.4 over CUDA-Q and Õ5 over QuEST for the random circuit. For the QAOA circuit, the speedup reached Õ5.6 compared to CUDA-Q and Õ4 compared to QuEST. In addition, Qaptiva HPC was able to emulate one more qubit than CUDA-Q and QuEST when using the same computational resources.
As shown in Figures 11 and 12, Qaptiva HPC consistently achieves lower emulation times than QuEST and CUDA-Q across all evaluated scenarios. Moreover, Qaptiva HPC can emulate one additional qubit compared to both emulators using the same number of nodes, resulting in increased computational efficiency and scalability.

Comparative heatmap of emulation times for the QAOA circuit using CUDA-Q, Qaptiva HPC, and QuEST across 30–35 qubits and 1, 2, 4, 8, and 16 nodes.

Comparative heatmap of emulation times for the Random circuit using CUDA-Q, Qaptiva HPC, and QuEST across 30–34 qubits and 1, 2, 4, and 8 nodes.
Starting at 31 qubits, this increase in the number of qubits emulated is reflected in the figures through the division of the Qaptiva HPC column into two subsets: one corresponding to results obtained using the same number of nodes as QuEST and CUDA-Q, enabling a direct comparison, and another showing the results achieved with fewer nodes, further highlighting the efficiency of the emulator.
For the QAOA circuit, the analysis extends up to 16 nodes, whereas for the random circuit, the experiments cover configurations of up to 8 nodes. QuEST was not run at 16 nodes for QAOA because its execution time would have exceeded the allotted time limit. Nevertheless, the available results indicate that Qaptiva HPC achieves lower execution times and supports a higher maximum number of emulable qubits than both CUDA-Q and QuEST within the range of configurations analyzed.
Figure 12 presents the corresponding heatmap for the random circuit, revealing trends similar to those observed in the QAOA circuit. An important observation is that, unlike in Figure 11, CUDA-Q achieves a lower runtime for the random circuit than for the QAOA circuit, whereas Qaptiva HPC and most notably QuEST exhibit higher runtimes for the random circuit. This difference may be attributed to the way each emulator manages inter-node communication and multi-qubit gates, which are more prominent in the random circuit and can affect performance depending on the underlying execution model.
5.3. Qaptiva 804 quantum emulation appliance
To establish a single-node performance baseline without GPU acceleration or multi-node capabilities, an additional experiment focused solely on CPU-based emulation was conducted. This scenario enables the assessment of the native efficiency of various emulators before incorporating the optimizations provided by Qaptiva HPC and MPI communication improvements.
Two quantum emulators were evaluated: PennyLane (using lightning.qubit), and Qaptiva in its CPU mode. The experiments were performed on a supercomputer based on the Qaptiva 804 architecture.
To ensure fair comparability, the MQT Bench78,79 and specifically designed for systematic evaluation of quantum software tools was used. The characteristics of the circuits evaluated are shown in Table 5.
Due to the steep exponential scaling of PennyLane’s execution times, emulations with more than 20 qubits could not be completed for the full set of circuit evaluated circuit types. In contrast, Qaptiva successfully reached 30 qubits across all benchmarks.
Figures 13 and 14 illustrate the execution time trends for the HHL and QNN circuits, respectively, relative to the system size. While runtimes are comparable between PennyLane (dashed line) and Qaptiva (solid line) at lower qubit counts (

Comparison of runtime as a function of the number of emulated qubits (5 to 30 qubits) for the HHL circuit using PennyLane, and Qaptiva.

Comparison of runtime as a function of the number of emulated qubits (5 to 30 qubits) for the QNN circuit using PennyLane, and Qaptiva.
In contrast, the QAOA circuit presented in Figure 15 displays a different behaviour for smaller circuit sizes. For lower qubit counts (

Comparison of runtime as a function of the number of emulated qubits (5 to 30 qubits) for the QAOA circuit using PennyLane, and Qaptiva.
Overall, the QAOA circuit exhibits the most homogeneous behaviour between the two emulators at lower scales, whereas HHL and QNN show pronounced differences in computational efficiency as circuit complexity increases. As detailed in Table 5, these performance disparities occur despite the circuits having relatively modest depths: 9 for QNN, between 31 and 217 for HHL depending on qubit count, and between 21 and 97 for QAOA up to 30 qubits.
6. Conclusions and future work
This study presents a review of state-of-the-art quantum emulation software for HPC clusters, considering metrics such as parallelization, precision, acceleration via GPU, emulation with noise, compatibility with queue schedulers, scalability in the number of qubits, and technical support. The comparative analysis evaluates four quantum emulation frameworks for HPC (QuEST, Qaptiva HPC, CUDA-Q, and PennyLane) across three hardware platforms with distinct characteristics: two HPC clusters (Spartan-Eviden and Joliot-Curie TGCC) and one quantum emulation appliance (Eviden Qaptiva 804). It should be noted that the scope of this analysis and the conclusions drawn are fundamentally tied to the state-vector emulation paradigm. Furthermore, due to the distinct software stacks and compatibility constraints of these systems, not all emulators could be deployed on every platform. Consequently, this study focuses on platform-specific comparisons, ensuring that each framework is evaluated within its supported environment rather than attempting a universal cross-platform benchmark.
In the Spartan-Eviden cluster, the DLinAlg emulator (Qaptiva HPC) outperformed QuEST across all evaluated configurations from
On the Joliot-Curie TGCC platform, CUDA-Q consistently achieved the lowest execution times for single-node GPU emulation, with average speedups of approximately Õ2 over Qaptiva HPC and Õ5 over QuEST for random circuits, and Õ3 and Õ20, respectively, for QAOA circuits. This demonstrates the effectiveness of CUDA-Q for single-GPU scenarios where inter-node communication is not required.
In distributed multi-node GPU configurations on the Joliot-Curie TGCC platform, Qaptiva HPC outperformed other systems, particularly as communication demands increased. With eight nodes, Qaptiva HPC achieved speedups of Õ1.4 over CUDA-Q and Õ5 over QuEST for random circuits, and Õ5.6 and Õ4, respectively, for QAOA circuits. In addition, Qaptiva HPC was able to emulate one additional qubit compared to CUDA-Q and QuEST when using the same computational resources, highlighting its efficiency in managing inter-node communications and distributed state-vector operations.
On the Qaptiva 804 appliance, Qaptiva exhibited greater scalability than PennyLane, particularly in the HHL and QNN benchmarks. As the qubit count increased, Qaptiva mitigated the exponential runtime growth observed in PennyLane, achieving speedups of
Across all platforms, the results highlight a fundamental trade-off between compute throughput and communication overhead. GPU-accelerated emulators dominate when computation is the bottleneck, whereas CPU-based multi-node frameworks excel when communication is efficiently managed. This reinforces the idea that the optimal emulator–hardware pairing is workload-dependent rather than universally optimal.
The analysis consistently showed that the circuit depth and gate count directly impact the emulation performance across all platforms. Random circuits, with their substantially greater depth and more than 500% increase in total gate count compared to QAOA circuits, exhibited significantly higher execution times and amplified performance differences between the emulation frameworks.
This study provides HPC centers and researchers with practical insights into selecting quantum emulators based on their specific hardware configurations and computational requirements. The results demonstrate that no single emulator dominates across all scenarios: CUDA-Q excels in single-GPU environments, Qaptiva HPC shows advantages in distributed multi-node configurations (both CPU and GPU). A multi-platform, multi-emulator comparison strengthens the robustness and representativeness of the analysis, contributing to a more comprehensive understanding of the current landscape of quantum emulation in HPC.
A limitation of this study is that it focuses exclusively on state-vector emulation, thereby excluding alternative emulation strategies such as tensor networks, stabilizer methods, path-integral approaches, and hardware-specific noise models. In addition, the evaluated circuits cover representative but not exhaustive algorithmic families, meaning that performance trends may differ for deep, highly entangled, or communication-heavy workloads. These aspects should be explored in future comparative studies.
While this study focuses on the state-vector emulation paradigm, future work could extend the comparative analysis to alternative emulation approaches, such as tensor network methods or stabilizer emulations, which may offer advantages for specific circuit families or qubit counts beyond the state-vector memory limitations. In addition, evaluating noisy quantum emulation capabilities across different platforms represents a promising research direction. Other research directions emerging from this work include (1) investigating hybrid CPU–GPU configurations to optimize resource utilization across heterogeneous HPC architectures, (2) developing an adaptive framework that dynamically selects the most efficient emulator based on circuit characteristics and available hardware resources, (3) evaluating the performance of emerging quantum emulation frameworks and their scalability in exascale computing environments, (4) conducting comprehensive energy efficiency analyses to assess the power consumption trade-offs of different emulation approaches, (5) developing standardized benchmarking methodologies that enable fair and reproducible comparisons across diverse HPC infrastructures and quantum emulation frameworks.
Footnotes
Funding
The authors disclosed receipt of the following financial support for the research, authorship, and/or publication of this article: This project was provided with computer and storage resources by GENCI at TGCC thanks to the grant ANR-22-PNCQ-0002 on the supercomputer Joliot-Curie.
Declaration of conflicting interests
The authors declared no potential conflicts of interest with respect to the research, authorship, and/or publication of this article.
