-
Notifications
You must be signed in to change notification settings - Fork 4
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
improve qisjob speed 😅 #16
Comments
I think it's probably the imports at the head of the file. |
For the record, there is no denying the great advantage potential qisjob offers, in allowing to communicate to different types of backends. But right now I am just interested in qisjob because of its interface, and will using only the IBM machines, in the exported python app. If we could make this simpler (perhaps slightly more limited version in this sense) and more performant, that would be really nice 👌 |
Hmm, well, there's one theory shot to Hades ... I profiled the import stage of the auxiliary libraries and here's the output.
|
hum... curious and curiouser...
|
Yes, well, you're not counting the time it takes to load Python. |
that is a good point. However, I just tried that:
edit:
Dang it. How am I going to get around this corner now? |
Well, you could rewrite qiskit in straight C. People have thought of doing that. |
|
thanks, again, you for this. |
dear @jwoehr, I've finished the speed tests of all the possible combinations of software and externals I've been working with (in combination and each on its own) and realized that the ones that involve qisjob are the slowest. I noticed that even just running qisjob on its own, i can never get execution time bellow 1.3 seconds:
time qisjob -a --qasm_simulator -t 2000 onebit.qasm
. If you think you could have an insight into why this may be, and that you can find a fix for it, I'd be happy to continue testing with a newer versions. Thank you again for this :)The text was updated successfully, but these errors were encountered: