perf(concurrency): use safe auto worker limits by default - #184
Merged
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
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.
Summary
--threadsoption useauto.Benchmark basis
The memory benchmark matrix supports a four-worker small-file cap.
At 900 KiB, four workers used about 2.31 GiB median peak RSS.
Eight workers used about 3.92 GiB median peak RSS.
At 1023 KiB, four workers used about 2.82 GiB median peak RSS.
Eight workers used about 4.03 GiB median peak RSS.
The default policy stays conservative.
Users can pass
--threads Nwhen they accept the resource cost.Validation
npm run lintnpm test -- --runInBandnode ./lib/src/lint-md.js README.mdRedactions
None.