HORIZON-EUROHPC-JU-2024-BENCHMARK-05-03

A European Benchmarking Framework for hybrid quantum-classical computing -

About the connections

The graph above was generated based on the following links

Call text (as on F&T portal)

View on F&T portal

Expected Outcome:

  • Enhanced evidence-based decision making through comprehensive system comparison that improves the procurement process for quantum-accelerated supercomputers (hybrid HPC-QC). This will enable more informed choices regarding the acquisition of new systems and upgrades of existing ones
  • Overall improved operation and fine-tuning of hybrid HPC-QC systems leading to improved performance, throughput and energy optimization, and improved end-user experience
  • Enhancing the competitiveness of EU quantum suppliers through transparent benchmarking of industrially relevant workflows
  • A unified, extensible and well-documented benchmarking framework to easily accommodate new, community-contributed benchmarks with common standards, versioning and control
  • A well-maintained and continuously updated benchmarking suite for QC- and hybrid HPC-QC workflows with open-source reference implementations for every benchmark, SDK-agnostic specifications and sample datasets
  • Active contributions to European and global standardisation on QC-, and hybrid HPC-QC benchmarking, certification and sustainability via standardisation bodies such as IEEE P7130/P7131, CEN-CENELEC JTC22-WG3, IEC/ISO JTC3 etc.

Scope:

A.) Development of a benchmarking framework addressing the following aspects:

  • offer a fine grained and fair comparison methodology among different systems and integration approaches, i.e. all benchmarks, benchmark run rules[1] and benchmark submission rules must be designed to ensure reproducibility, repeatability and replicability of metrics on the same system, ensuring fairness and comparability of metrics across different systems
  • define and continuously update a precise and relevant performance metrics catalogue
  • standardise all benchmarking input- and output formats
  • collect and report all benchmarking results while offering statistically sound result analyses
  • ensure that all benchmarks are executable on the respective target environment(s)
  • offer a standardized structured workflow capturing and streamlining the entire benchmarking process
  • offer a standardised repository with transparent version control
  • provide at least one reference implementation based on an EU SDK for each benchmark
  • is of production-quality and ready to assess all of EuroHPC’s QC- and hybrid HPC-QC systems
  • provide all required templates with relevant input data to properly execute the benchmarking suite on every EuroHPC system.

The benchmarking framework along with its workflows will be realised in a software implementation that offers to the end-user a dynamic workspace for the entire workflow.

B.) Establishing a comprehensive QC- and hybrid HPC-QC benchmarking suite utilizing the framework developed in the first objective. This benchmarking suite, with its associated performance metrics, will be designed to measure and assess the performance of QC- and hybrid HPC-QC systems.

The envisioned benchmarking suite is expected to:

  • be generally hardware agnostic, enabling cross-device verification (e.g. via entangled-state comparisons, or distributed inner-product tests)
  • provide thorough documentation for developers and end-users
  • develop novel hybrid HPC-QC benchmarks within the following three key areas:
    • Throughput: capturing true end-to-end performance including queue-to-result latency, provisioning delays and data movement overhead
    • Latency: queue-to-solution time, end-to-end (i.e. submission-to-result)
    • Energy: per-shot energy, cryogenic overhead, control-electronics draw, classic-compute share, energy-to-solution (incl. all contributions, i.e. quantum-core, cryogenic, control electronics, classical compute)
  • catalogue relevant, well-established QC benchmarks from across the entire software stack, e.g.:
    • Component level/ Gate level: gate fidelities, connectivity, energy-state relaxation time, coherence (T1/T2), randomized benchmarking (RB), cross-talk RB, error-per-layered-gate (EPLG), logical-error rate, logical error scaling (Λ)
    • System level: Clifford-volume, cross-entropy (XEB), CLOPS/ rQOPS, MegaQuOp, GHZ-state fidelity (single shot read-out)
    • Software/ Compiler level: error-syndrome mapping, decoding-throughput metrics, quantum compilation volumetric benchmarks
    • Application layer: VQE, QAOA, MaxCut, Q-Score, quantum-enhanced ML, Monte Carlo sampling, workload-specific benchmarks, quantum application score
  • support of both noisy-intermediate-scale-quantum (NISQ) and fault-tolerant-quantum-computing (FTQC) regimes (e.g. logical-error rates, logical-clock rate, decoding throughput)
  • ensure that each benchmark produces at least one metric
  • define reliable and common metrics to compare different qubit modalities, as well as the depth of the HPC-QC integration based on pre-defined criteria (e.g. efficiency)
  • ensure the scalability of each benchmark by identifying relevant scale parameters

Proposals should provide a thorough justification for the selection of each benchmark and performance metric, clearly explaining how they align with the specific requirements and priorities of the European HPC-QC landscape. The inclusion or integration of existing benchmarks under the umbrella of this initiative is clearly foreseen, provided there are prior agreements with the benchmark owners and compatibility with licensing conditions.

The proposal must also outline a clear IP plan and licensing strategy under the European Union Public Licence (EUPL-1.2) to safeguard openness and promoting European industrial uptake enabling first exploitation within EU- and Participating States.

The project will also propose and maintain a detailed strategic development roadmap for the action, which:

  • anticipates future developments in QC and hybrid HPC-QC, including emerging technologies
  • foresees the hardware agnostic and hardware inclusive support of hybrid HPC-QC systems
  • The consortium will actively engage with industry and research communities through workshops, working groups, and feedback loops to receive continuous feedback ensuring that all benchmarks are relevant and up to date.

    Requirements:

  • The proposal shall take into consideration the state of the art of development quantum computing benchmarking
  • Define a mechanism to monitor the benchmarking framework and pool appropriate existing benchmark suites, relevant for architectures of all participating HPC-QC centres for deployment in a common data repository
  • The benchmarking framework and the encompassing benchmarking suite will be made available to the user communities under the European Union Public Licence (EUPL).
  • [1] run rules define required and forbidden hardware, software, optimization, tuning, and procedures.

    News flashes

    2026-04-11
    The submission session is now available for: HORIZON-EUROHPC-JU-2024-BENCHMARK-05-02, HORIZON-EUROHPC-JU-2024-BENCHMARK-05, HORIZON-EUROHPC-JU-2024-BENCHMARK-05-03
    call topic details
    Call status: Open
    Opening date: 2025-12-11 (4 months ago)
    Closing date: 2026-04-14 (2 days from now)
    Procedure: single-stage

    Budget: 2,000,000
    Expected grants: 1
    Contribution: 500,000 - 1,000,000
    News flashes

    This call topic has been appended 2 times by the EC with news.

    • 2026-04-11
      faq for the call: horizon-eurohpc-ju-202...
    • 2026-04-11
      the submission session is now available...
    Call

    HORIZON-EUROHPC-JU-2024-BENCHMARK-05

    Call topics are often grouped together in a call. Sometimes this is for a thematic reason, but often it is also for practical reasons.

    There is 1 other topic in this call:

    Source information

    Showing the latest information. Found 10 versions of this call topic in the F&T portal.

    Information from

    • 2026-03-26_06-33-26
    • 2026-03-25_06-34-19
    • 2026-03-19_06-34-15
    • 2026-03-03_06-33-53
    • 2026-01-06_06-31-09
    • 2025-12-24_06-31-05
    • 2025-12-23_06-31-13
    • 2025-12-17_06-30-58
    • 2025-12-16_06-31-04
    • 2025-12-12_06-30-43

    Check the differences between the versions.

    Annotations

    You must be logged in to add annotations
    No annotations yet

    Events

    This is just a very first implementation, better visualisation coming

    Events are added by the ideal-ist NCP community and are hand-picked. If you would like to suggest an event, please contact idealist@ffg.at.

    Call topic timeline

    What phase of the topic timeline are we in? This timeline contains some suggestions on what are realistic actions you should or could take at this moment. The timeline is based on the information provided by the call topic.
    1. Work programme available

      - 6 months ago

      The call topics are published first in the Work Programme, which is available a while before the call opens. By following up the Work Programme publications, you can get a headstart.

    2. Opening date

      - 4 months ago

      The call opened for submissions.

    3. Publication date

      - 3 months ago

      The call was first imported in TopicTree.

    4. Today

    5. Closing date

      - 2 days from now

      Deadline for submitting a project.

    6. Time to inform applicants Estimate

      - 5 months from now

      The maximum time to inform applicants (TTI) of the outcome of the evaluation is five months from the call closure date.

    7. Sign grant agreement Estimate

      - 8 months from now

      The maximum time to sign grant agreements (TTG) is three months from the date of informing applicants.

    Funded Projects

    Loading...

    Project information comes from CORDIS (for Horizon 2020 and Horizon Europe) and will be sourced from F&T Portal (for Digital Europe projects)

    Call document info

    This section will come soon and contain the scraped information from the call document, such as the expected impact, scope, and other relevant sections. In the meantime, you can find this information in the call text section or directly on the F&T portal. View on F&T portal