Feat: sort the recorded data in memory #115
Merged
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
pangdayuan1
requested review from
binyu1005,
srotony,
wildeslam and
QizhengMo
|
Kudos, SonarCloud Quality Gate passed!
|
srotony
approved these changes
Nov 20, 2023
binyu1005
approved these changes
Nov 20, 2023
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, sorting was done by the record and creation indexes, but now it is done in memory because it is faster in memory.
80 link data, cost 186ms with indexing, cost 134ms with sorting in memory.
200 link data, cost 240ms with indexing, cost 156ms with sorting in memory