[WIP] Update least_busy #2288
Closed
[WIP] Update least_busy #2288
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kt474
added
the
Changelog: New Feature
ElePT
removed
Changelog: New Feature
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This is currently more of a proof of concept to show that we can get the least busy backend (based on queue length) with just the
/backendscall. This would be much cleaner if we wait until we strip out the IQP classic code. Then we can properly updateservice.backends()to accept the newBackendsResponseV2. From initial testing, fetching the least busy backend only takes 1-2 seconds now.https://quantum.cloud.ibm.com/api/docs/?urls.primaryName=2025-05-01+%E2%80%93+Today
Details and comments
Fixes #