Refactor ANN code to avoid rvalue references.#2259
Merged
rcurtin merged 3 commits intomlpack:masterfrom Mar 11, 2020
Merged
Conversation
Member
Author
|
(I posted another timing comment earlier, but I was not able to reproduce the numbers so I deleted it. It must have been a system issue or something.) I ran the and on this branch: Over several trials both versions came out with about the same runtime (plus or minus 3 to 5 seconds). |
Member
Author
Member
zoq
approved these changes
Mar 9, 2020
Member
zoq
left a comment
There was a problem hiding this comment.
Wow, quite a few changes; looks good to me.
This was referenced Mar 12, 2020
Closed
Merged
This was referenced Mar 12, 2020
Closed
Closed
Closed
Closed
Closed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously, all of the ANN code had signatures like
but the use of rvalue references led to some incorrect memory usages, and it was a little confusing as people would call
Forward(std::move(input), std::move(output))... butinputwould remain unchanged (this is confusing given the expectedstd::move()semantics).In this PR I've refactored out all unnecessary use of rvalue references. I think, in some places, this makes copies avoidable and there may be some minor acceleration. I'm running some quick benchmarks in the
models/repo and will post the results here when they're done (I don't expect any serious speedup).