Reduce regexps computed for parsing kramdown lists #596
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.
Rationale
Interpolated regular expressions within a frequently called method allocates memory for each generated expression. When possible, interpolation can be limited to just once by using the
/o
flag. But that is not possible in this situation.While profiling the build for Jekyll's documentation site (via
memory_profiler
), I came across this hot path where the regex/^( {0,1}[+*-])([\t| ].*?\n)/
was allocated a significant amount of times closely followed by/^( {0,2}[+*-])([\t| ].*?\n)/
among a few others.If it is of any relevance, the summary from the profiling is:
Before
After