Add optional forward and backward thread pools #28
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Want to write a benchmark to see whether reusing a thread pool noticeably improves performance? |
|
Creating and destroying a |
akshayka
approved these changes
Jan 3, 2020
There was a problem hiding this comment.
In the future, if we find ourselves wanting to add more arguments, it might make sense to create a Workspace class containing things like threadpools. Then solve_and_derivative would take a handle to a workspace (which might be None), and there'd also be a function that would initialize and return a workspace that could be reused across calls.
|
Closing this PR without merging. I don't think it's necessary at this point. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.