Fix -P1 crippling performance via 32 MiB working-set cap (#13) - #15
Open
PierreLvx wants to merge 1 commit into
Open
Fix -P1 crippling performance via 32 MiB working-set cap (#13)#15PierreLvx wants to merge 1 commit into
PierreLvx wants to merge 1 commit into
Conversation
PROCESS_MODE_BACKGROUND_BEGIN lowers the process's memory priority, which makes Windows cap the whole process's working set at ~32 MiB - causing 250x-800x slowdowns once compression/decompression touches more memory than that. Use THREAD_MODE_BACKGROUND_BEGIN per worker thread instead, which gives the same lowered CPU/disk I/O priority without the working-set cap side effect. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.
PROCESS_MODE_BACKGROUND_BEGIN lowers the process's memory priority, which makes Windows cap the whole process's working set at ~32 MiB - causing 250x-800x slowdowns once compression/decompression touches more memory than that. Use THREAD_MODE_BACKGROUND_BEGIN per worker thread instead, which gives the same lowered CPU/disk I/O priority without the working-set cap side effect.