-
Notifications
You must be signed in to change notification settings - Fork 3
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
Backend performance #57
Comments
They all seem almost two orders of magnitude slower than in the original |
Probably it could be related to the fact that the benchmark was performed on different CPUs. I've obtained this data by running on my laptop. I will try to repeat the benchmark on the cluster. |
Thanks for the interesting result! @andrea-pasquale whenever you can, would you try to rerun with many more repetitions? (e.g. with 200). Otherwise, if you update/share your script and lock file (or confirm you're just using the Qiboml's one), I could even dispatch it myself, of course.
That's also certainly interesting, since the current plot is just stopping on the intersection. Thanks again :) |
I did a benchmark to check how fast are the backends which are currently available in qiboml. I've just executed a QFT for different number of qubits.
It is interesting how JAX performed relatively bad for low number of qubits, but at around 20 qubits it seems to match the performances of the other backends.
Here is the code used for the benchmark.
Whenever I have time I can start looking at the JAX backend to see if we can improve the performance.
The text was updated successfully, but these errors were encountered: