Optimize Sdf_PathNode::GetPathToken() by avoiding unnecessary memory allocation #3312
+9
−2
Conversation
This file contains 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
…allocation when the token already exists
|
Filed as internal issue #USD-10180 |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Description of Change(s)
GetPathToken no longer does a memory allocation when the token already exists. A benchmark that calls SdfPath::GetString repeatedly on a large amount of SdfPaths shows 2.3x improvement on Windows.
Note that the following unit tests fail on Windows with or without the changes:
158 - testWorkThreadLimitsRawTBBMax (Failed)
767 - testUsdviewNavigationKeys (Failed)
783 - testUsdResolverExample (Failed)
Fixes Issue(s)
None.