Skip to main contentIBM Quantum Documentation

Reserve system time


This feature is available only to organizations that belong to the IBM Quantum™ Network(opens in a new tab). Educators and researchers can also make reservations and access other benefits by signing up for one of the special programs we offer. Go to the Educators program sign-up form(opens in a new tab) or the Researchers program sign-up form(opens in a new tab) for more information.

Under standard operating conditions, IBM Quantum systems accept jobs according to the dynamic priority assigned by the fair-share queuing system.

A job enters the queue and joins other jobs from various instances.  The job that entered the queue first exits the queue and is sent to a backend.
Normal device-queuing operation

While this system attempts to balance workloads for the benefit of all users, there are often use cases where you may require limited-time access at a higher priority level. IBM Quantum provides an option to gain elevated access to specific systems over a specified period of time: Dedicated mode. Depending on your hub configuration, if you are a hub admin or group admin, you can reserve time in advance on a particular system with the Systems Reservations tool.

Example use cases for dedicated mode include the following:

  • In-class demonstrations
  • Iterative and near-time compute algorithms
  • Jobs involving detailed noise analysis
  • Time-critical projects
System reservations and fair-share allocation

System time accumulated while using system reservations counts toward an instance’s fair-share allocation amount.

If you need sole access to a specific quantum system for a given instance, select dedicated mode when making a reservation (only available to members of the IBM Quantum Network(opens in a new tab)).

A job enters the queue and joins other jobs from various instances.  The jobs that are sent from Instance 2 are all processed in their own dedicated queue while jobs from other instances wait in the normal queue.
Instance #2 in dedicated mode

The standard fair-share queue is always blocked when the device is in dedicated mode.

A job enters the queue and joins other jobs from various instances.  There are no jobs from Instance 2.  Because the backend is in dedicated mode for instance 2, no jobs are processed. All jobs wait in the normal queue.
Dedicated mode with no dedicated jobs

Dedicated mode with no dedicated jobs from instance #2 leaves the device idle.

This allows users to implement algorithms where input circuits are conditioned on previous results, such as iterative and near-time compute methods, without having to wait for other users’ results to process. If the dedicated instance has multiple users, then a single user’s jobs may be queued behind those of other users in the instance, as the execution is first-in first-out.

Was this page helpful?