Optimize parsing #124
Open
Optimize parsing #124
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
A few changes: 1. Switch from `multiprocessing` to `concurrent.futures` with `ProcessPoolExecutor`. This is just to make the code easier to work with. 2. Perform `check_file()` as results return to the main process, in order to reduce peak memory usage. Previously all parsed files were kept in memory before being checked, leading to massive memory usage. 3. Construct parsers once per process, rather than once per file. Previously parser construction took ~5% of the runtime, this reduces it to a constant amount. Benchmarked on a project with 238 templates. Before: ``` $ time curlylint templates/**/*.html All done! ✨ 🍰 ✨ curlylint templates/**/*.html 352.25s user 3.37s system 999% cpu 35.575 total ``` After: ``` $ time curlylint templates/**/*.html All done! ✨ 🍰 ✨ curlylint templates/**/*.html 324.22s user 2.79s system 995% cpu 32.858 total ``` ~8% of the time saved. The parser remains quite slow, I think it does an unfortunate amount of backtracking.
adamchainz
force-pushed
the
optimized_concurrent
branch
from
130b9a6
to
670c03d
Compare
|
Okay turns out a lot of tests call |
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.
A few changes:
multiprocessingtoconcurrent.futureswithProcessPoolExecutor. This is just to make the code easier to work with.check_file()as results return to the main process, in order to reduce peak memory usage. Previously all parsed files were kept in memory before being checked, leading to massive memory usage.Benchmarked on a project with 238 templates.
Before:
After:
~8% of the time saved.
The parser remains quite slow, I think it does an unfortunate amount of backtracking.