Restructure execution modes #2565
Draft
+87
−61
Conversation
This file contains 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
|
|
||
| | Mode | Benefits | | ||
| |---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ||
| | Batch | ● The entire batch of jobs is scheduled together and there is no additional queuing time for each.<br></br>● The jobs' classical computation, such as compilation, is run in parallel. Thus, running multiple jobs in a batch is significantly faster than running them serially.<br></br>There is usually minimal delay between jobs, which can help avoid drift.<br></br>● If you partition your workload into multiple jobs and run them in batch mode, you can get results from individual jobs, which makes them more flexible to work with. | |
There was a problem hiding this comment.
Are the dots trying to recreate a list? We shouldn't do that because it doesn't comply with a) "semantic web" and b) Carbon design. Does it work to do this?
Suggested change
| | Batch | ● The entire batch of jobs is scheduled together and there is no additional queuing time for each.<br></br>● The jobs' classical computation, such as compilation, is run in parallel. Thus, running multiple jobs in a batch is significantly faster than running them serially.<br></br>There is usually minimal delay between jobs, which can help avoid drift.<br></br>● If you partition your workload into multiple jobs and run them in batch mode, you can get results from individual jobs, which makes them more flexible to work with. | | |
| | Batch | <ul><li>The entire batch of jobs is scheduled together and there is no additional queuing time for each.</li><li><p>The jobs' classical computation, such as compilation, is run in parallel. Thus, running multiple jobs in a batch is significantly faster than running them serially.</p><p>There is usually minimal delay between jobs, which can help avoid drift.</p></li><li>If you partition your workload into multiple jobs and run them in batch mode, you can get results from individual jobs, which makes them more flexible to work with.</li> | |
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.
closes #2133
preview: https://qiskit.github.io/documentation/pr-2565/guides/execution-modes