Minor optimizations #61
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Profiling shows that the majority of the time is spend in the gradient computation, which is to be expected. Sadly I wasn't able to improve this much for this PR.
I think that in principle a lot more optimization is possible, but that would require much more changes to the code. Basically, instead of separate log_p and gradient functions we'd need a class. That way, things like
total_lencan be easily computed once and cached, and the gradient vectorgradcan also be reused. In general, it should make memory reuse easier.For now, this PR implements:
finish()method ensures that all progress bars are completely filled at the end of the loop. Now it no longer does this if there was a user interrupt.Let's see if the R CMD CHECK runtime decreases (I doubt it though).