-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Fix performance of ReverseEstimatorGradient
for partial gradients
#9491
Conversation
Thank you for opening a new pull request. Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient. While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone. One or more of the the following people are requested to review this:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR LGTM, I know that the low performance has been an issue to run certain experiments, and it's great that you fixed it so fast!!!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Absolutely lol at that performance, haha. It happens because there's no __iadd__
method defined for QuantumCircuitData
, so the whole list gets copied and reassigned by +=
.
It's a shooting offence to mutate QuantumCircuit.data
directly.
Pull Request Test Coverage Report for Build 4053970489
💛 - Coveralls |
…Qiskit#9491) * Use append over += * add reno
…Qiskit/qiskit#9491) * Use append over += * add reno
Summary
The
ReverseEstimatorGradient
did a lot of unnecessary copies if the circuit contained many gates with respect to whose parameter we didn't derive. That meant that e.g. computing all derivatives of a 100-parameter circuit was faster than computing only a single derivative.Details and comments
The circuit splitting used
instead of just
subcircuit.append
. The first seems to copy all circuit instructions, which gets very expensive if called many times.Here's a profiling for computing 7 of ~100 parameters in an
EfficientSU2
circuit before the fix:and after