perf(fmt): prioritize Markdown worker tasks - #217
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
1 participant
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
This PR starts Markdown/MDX formatter tasks before other files when at least eight workers are active, reducing idle workers at the end of large formatting runs while preserving result order. The priority remains intentionally limited to Markdown because parser overrides and large JS/TS files make broader extension heuristics less predictable.
On Rspack (4,550 tasks, including 493 Markdown/MDX files), 12 alternating paired runs at 8 workers improved the formatter-stage median from 1,955 ms to 1,902 ms (2.74%, about 53 ms), with the prioritized order winning all 12 runs. Runs with 2, 4, or 6 workers showed no stable benefit, so smaller pools retain input order.