Skip to content
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

Improving solver speed #12

Open
cheater opened this issue Aug 23, 2017 · 0 comments
Open

Improving solver speed #12

cheater opened this issue Aug 23, 2017 · 0 comments

Comments

@cheater
Copy link
Contributor

cheater commented Aug 23, 2017

Following this technique: Detecting Space Leaks, I discovered that hvx seems to spend a lot of time in evaluate. At every step of eg subGradLoop, it has to evaluate the objective, look up functions, etc. My suggestion is to add an intermediate evaluation step, which compiles the objective down to a single function that just takes all the variables and applies it. This could have the added benefit of adding a layer in which other implementations of the arithmetic could be done if one wanted to do this, eg with cuda - instead of evaluating EAdd to GHC's + and similarly other functions we could compute a piece of code that would go to cuda. Eventually maybe the whole of subgradLoop could work on the gpu. Do you think such a pre-compilation step would be of benefit to the speed of hvx? Can you suggest other places to improve the performance?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant