Make matcher 120000% faster #560
Merged
Conversation
This file contains 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
Sharktheone
force-pushed
the
css/improve-matching-speed
branch
from
7f66b1c
to
4c45355
Compare
jaytaph
reviewed
Aug 22, 2024
| /// Parses the internal CSS definition file | ||
| #[memoize] | ||
| pub fn parse_definition_files() -> CssDefinitions { | ||
| fn pars_definition_files() -> CssDefinitions { |
There was a problem hiding this comment.
typo for parse_definition_files() ?
jaytaph
approved these changes
Aug 22, 2024
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.
The current matcher takes 55secs to validate the css from news.ycombinator.com (most of it is from useragent.css). Now it only takes ~40ms, and it takes 2.5 secs from start to the first rendered frame.