-
Notifications
You must be signed in to change notification settings - Fork 31
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
Bohrium 100 times slower than numpy, time "unaccounted for" #633
Comments
The problem is both in the openmp and opencl stack with pretty much the same cost (confirming that it's not execution time or fusion). |
This has been known for a long time (see #342). Here is a dump of
I think the time spent in Due to this overhead, I usually don't recommend using Bohrium for problem sizes < 1e6. |
Weirdly, the "unaccounted for" time decreases slightly also for this problem when I use |
When running with Bohrium or bh107, a crazy amount of time is being spent in "unaccounted for". The following code runs in 0.27 seconds in pure Numpy, but takes 25 seconds with both bohrium and bh107, despite only doing Bohrium-friendly operations, and the generated kernels being efficient. Where does the time go, and how do we fix this?
Switch between the backends by setting backend to "numpy", "bohrium", or "bh107".
The text was updated successfully, but these errors were encountered: