SVDirectionChange: Use reverse prefix max/min to query max/min position better - #4330
Draft
WilliamQiufeng wants to merge 2 commits into
Draft
SVDirectionChange: Use reverse prefix max/min to query max/min position better#4330WilliamQiufeng wants to merge 2 commits into
WilliamQiufeng wants to merge 2 commits into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This needs testing before being merged. It is not known yet if this brings remarkable improvements. Since this PR is created when I was trying to fix a bug with LN length with changing SSF, so I didn't really test this.
This PR calculates reverse prefix min/max
SVDirectionChange.PositionforSVDirectionChangesso that maximum/minimum position could be queried in O(1) after knowing the latest direction change.Furthermore, since
SVDirectionChangeusesStartTime, we could use binary search, so looking it up now only takes logarithmic time. So this basically makesSetEarliestAndLatestLongNotes()O(log n), where n is number of SV direction changes.