-
Notifications
You must be signed in to change notification settings - Fork 34
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
Migrate tutorials and a how-to guide to v2 primitives #552
Conversation
There will be no 0.22.1 release, it seems, but 0.23.0 is out now so we can use it instead.
Pull Request Test Coverage Report for Build 8741355357Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
but now it executes very slowly
With the change to a fake backend, the first tutorial notebook now takes over 15 minutes to execute on my laptop. 😭 EDIT: I changed to a 5-qubit fake backend, and now it runs within a reasonable time. |
Now the execution time is reasonable.
It appears there is no 0.14.0 release on pypi
With this change, the tutorials are a bit slower, but I think it is acceptable. It's just so nice to use Qiskit Runtime with fake backends everywhere. If a user wants to use a real backend, they need only modify the Before
After
|
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.
Just a note: there are much fewer single-qubit gates in transpiled_qc
after moving to FakeManilaV2
. The zoom level of that circuit ends up changing as a result, which can be noticed from the rich diff on github.
Agree with this. I really like the FakeBackends for demos for that same reason |
I'm seeing the same behavior on my end. I wonder if we should run some quick numbers and report this up. Maybe this is expected, but it seems like a massive slowdown over V1 EDIT: Only about 3 minutes on my end, but still much slower |
It is all a bit opaque to me, but here is what I suspect is happening: When we use a 5-qubit fake backend, the code simulates all 5 qubits, even when only 2 or 4 are in use, which can be a couple times slower. Plus, there might be some additional slowdown due to applying the noise model from the chosen fake backend. So in that sense it may not be surprising that it is slower to use a fake backend than a noiseless |
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.
This looks great, thanks for putting this together
I don't think the slowdown when trying to use FakeBackend
s with more qubits is something we can control.
This builds on #513 and follows https://docs.quantum.ibm.com/api/migration-guides/local-simulators.
I've added this to the 0.7.0 milestone, but it need not block the release because this portion can be moved to the 0.7.1 milestone and backported once it is ready.
.result()
to obtain them #509.Batch
mode instead ofSession
mode in cutting tutorials #535.Remaining action items