LogoLogo
  • Welcome to Quantum Cloud Services
  • Getting Started
    • Set up your environment
      • JupyterLab IDE
      • Install Locally
        • Quil SDK Docker Image
    • Quil SDK Overview
    • Running your first Quantum Program
  • Guides
    • Quil
      • What is Quil?
      • Language Support
      • Dynamic Control Flow
      • Customizing Program Readout
    • QPU vs. Simulator (QVM)
    • How to Use Rigetti QPUs
    • Access a QPU
      • QPU Reservations
      • On-Demand Access
      • QCS QPU Gateway
    • QCS Group Accounts
    • Interactive Tutorials
    • How Programs Are Built & Run
      • Execution and Request timeouts
    • The Lifecycle of a Program
    • The Rigetti QCS API
    • Using the QCS CLI
      • Using the Legacy QCS CLI
    • QCS Credentials
    • Benchmarking and Fidelity
  • Troubleshooting
    • Gathering Diagnostics
    • Report an Issue
  • Glossary
  • FAQ
  • References
    • pyQuil Reference
    • QCS API Specification
    • QCS CLI Reference
    • QCS Client Configuration
    • Quil / Quil-T Specification
    • quilc Reference
    • quil-rs Reference
    • QVM Reference
    • Rigetti Module for Cirq
    • Rigetti Provider for Qiskit
Powered by GitBook
On this page

Was this helpful?

  1. Guides

Access a QPU

PreviousHow to Use Rigetti QPUsNextQPU Reservations

Last updated 9 months ago

Was this helpful?

With an active , there are two ways to run your programs on a QPU:

  • Reserved access, during scheduled blocks of time, gives you priority access to that QPU for a period of time.

  • On-demand access, without a reservation, allows you to access a QPU at almost any time at lower priority.

Learn more about each mode here:

QPU Reservations

On-Demand Access

Which mode should I use?

On-demand is great for testing and executing individual programs or quick experiments with a small number of jobs and where performance (in terms of speed and waiting time) isn't a concern.

If you need any of the following, you may prefer to use a reservation:

  • a guarantee that your job will be run

  • to run many programs in a short period of time

  • to run programs in close subsequence with a minimum amount of time in between, such as for iterative workloads like VQE and QAOA

  • to work interactively, with a short development feedback cycle

With a reservation, your jobs are guaranteed to run as fast as possible and without interruptions. Per second of execution, reservation access is lower cost than on-demand access, if that reservation is fully used.

QCS account