-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Determine parallelization limit per machine #30
Comments
Note that PR #31 allows this parameter to be controlled at the command line. |
Hello, I'd like to give this a shot! A first approach could be a simple binary search over the range of possible values for The first hurdle for this ticket would be deciding what parallelized code should be benchmarked. A first pass could focus on a single thing, and later be expanded to include others. @stylewarning What do you think would be worth focusing on? Additionally, should this benchmarking happen as part of the |
I think there should be an option to |
As for the measurement to be done, I'd suggest doing some calculation that applies a 1q gate, and an operation that applies a 2q gate, and calculating |
The variable
*qubits-required-for-parallelization*
is statically set to19
, which means that as soon as 19 qubits is reached in a computation, the computations will be parallelized.This isn't ideal for all machines. Sometimes parallelization provides gains with values lower or higher than
19
. The goal of this issue would be to search for that crossing point and optimize accordingly.Problems that must be solved in order to solve this issue:
The text was updated successfully, but these errors were encountered: