About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Minimize job run time
There are several ways you can limit the amount of quantum time spent processing and running a job:
-
Run only as many iterations and shots as you need: The time your workload takes (and therefore, its cost) depends on how many jobs you create in a session and how many shots are run in each job. Therefore, you can manage your cost by running only as many jobs and shots as you need.
-
Set limits on execution time: You can limit how long each job or session runs. For details, see Maximum execution time for a Qiskit Runtime job or session.
-
Use only the necessary settings for error suppression, error mitigation, and optimization, because higher values can cause your jobs to run longer. See Algorithm tuning options, Configure runtime compilation, and Configure error mitigation for details.
Next steps
Recommendations
- Workload usage.
- Explore error mitigation in the Cost functions course.
Was this page helpful?
Report a bug or request content on GitHub.