tsort: drastically reduce memory copies#5969
Merged
sylvestre merged 1 commit intouutils:mainfrom Feb 11, 2024
Merged
Conversation
af84d79 to
7ab563a
Compare
Contributor
|
Nice, please set a fixed seed for reproducibility tho :) |
Collaborator
Author
|
Fair :) |
7ab563a to
e0c2714
Compare
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.
To reduce the copying happening in
tsort, we can load the entire input in memory and only refer to slices within that input instead of allocating aStringfor each occurrence of a node.cc @anastygnome
On my input generated with:
The time measured with hyperfine drops from ~2.3 seconds to ~1.6 seconds.