perf: Avoid re-canonicalizing the entire IntervalSet on push#1308
Open
Marwes wants to merge 2 commits into
Open
perf: Avoid re-canonicalizing the entire IntervalSet on push#1308Marwes wants to merge 2 commits into
Marwes wants to merge 2 commits into
Conversation
Canonicalize is taking up a significant amount due to a regex with a huge amount of character ranges (generated by [lalrpop](https://github.com/lalrpop/lalrpop)'s lexer expanding multiple `\w` in a token). While this could perhaps be fixed in lalrpop I did notice the TODO in the code and after addressing this so we automatically union and compress on each push instead of re-canonicalizing on every push and that fixed the performance problem. I did see the earlier attempt at this rust-lang#1051 and it seems like that was reverted and regression tests were added so I hope that and the existing tests are enough (I don't have a clear idea on what tests might be missing).
b3ea20f to
3d44573
Compare
Contributor
Author
|
I have done some optimization around the code where this occurs which brings up |
BurntSushi
requested changes
May 21, 2026
Member
BurntSushi
left a comment
There was a problem hiding this comment.
Hi! Yes, thank you and apologies for the late reply.
The change here itself looks good to me. Thank you for working through this subtle optimization. :-) I have only minor nits on this PR and a request.
Could you add a benchmark to rebar? I think probably this directory is the place to add it. And if you could show a before-and-after on the rebar results here, that would be great.
Marwes
added a commit
to Marwes/regex
that referenced
this pull request
May 26, 2026
Just noticed the comment while doing rust-lang#1308 but I don't have any actual case where this shows up as performance problem. I would argue the code is simpler though so perhaps just simpler code and removal of a "TODO" comment is good.
Marwes
added a commit
to Marwes/regex
that referenced
this pull request
May 26, 2026
Just noticed the comment while doing rust-lang#1308 but I don't have any actual case where this shows up as performance problem. Arguably the code is simpler though so perhaps that and the removal of a "TODO" comment is good.
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.
Canonicalize is taking up a significant amount due to a regex with a huge amount of character ranges (generated by lalrpop's lexer expanding multiple
\win a token). While this could perhaps be fixed in lalrpop I did notice the TODO in the code and after addressing this so we automatically union and compress on each push instead of re-canonicalizing on every push and that fixed the performance problem.I did see the earlier attempt at this #1051 and it seems like that was reverted and regression tests were added so I hope that and the existing tests are enough (I don't have a clear idea on what tests might be missing).