perf: optimize map iteration and string handling in n-quad parsing #85
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
- Use direct map iteration in DeepCompare - Add explicit string handling in normalizeValue to avoid unnecessary and slow formatting For example, parsing ~60k n-quads on an AMD Ryzen 7 PRO 8840U now takes 1.7s, down from 5.3s (a ~68% reduction). Co-authored-by: Alex Borodin <alex.borodin.ext@siemens.com> Signed-off-by: Alex Borodin <alex.borodin.ext@siemens.com> Signed-off-by: Michael Adler <michael.adler@siemens.com>
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.
Summary
Basic example
This doesn't change existing behavior.
Motivation
Performance :)
For example, parsing ~60k n-quads on an AMD Ryzen 7 PRO 8840U now takes 1.7s, down from 5.3s (a ~68% reduction).
Checks
make test