-
Notifications
You must be signed in to change notification settings - Fork 26
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
Speed of QP solver is very slow #16
Comments
What is this story about? Could you provide more context?
|
Before Harry's fix in lava-nc/lava#87, the CSP based implementation was 5000x slower than pure numpy implementation as pointed out in lava-nc/lava#36. After the fix there is an ~50x improvement in speed as compared to before but it's still 100x slower than a pure numpy implementation. (Intel Core i5-5257U with 8GB RAM, running Ubuntu 20.04.2 LTS with lava v0.2.0 vs v0.1.1) |
@ashishrao7 what is the status of this issue? was there any progress or is the SW lava backend still slower than numpy? |
No the software backed is now much faster than it was when the issue was made. I think the speed issue after Harry's fix was because of a hacky primitive profiling tool that I had developed and was using. One also has to keep in mind that using get()/set() can also make it slow because of the serial nature of get()/set(). Closing this issue now. |
The functioning of the QP solver is extremely slow compared to a pure numpy implementation. This is in reference to Issue lava-nc/lava#36
The text was updated successfully, but these errors were encountered: