docs: sync after #87 (RunspacePool memory rule of thumb correction) - #90
Merged
Conversation
PR #87 (WinPSCompat-Session-Leak fix, merged 2026-07-30) added measurement data showing in-process pool runspaces cost 1.2-1.4 MB each, not ~30 MB. The 30 MB figure came from the process-spawn path and does not apply to the RunspaceExecutionEngine's pool. The "Default-Tuning für 500-par.-WF-Topologie" section still carried the old rule of thumb, producing contradictory guidance within the same document. Corrected to match the 2026-07-30 measurement already present later in the file.
4 tasks
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
2 participants
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.
What & why
PR #87 (WinPSCompat-Session-Leak fix, merged 2026-07-30) added measurement data to
docs/performance-improvements.mdshowing that in-process pool runspaces cost 1.2–1.4 MB each, not ~30 MB. The 30 MB figure came from the process-spawn path (pwsh.exe/powershell.exeper step) and does not apply to theRunspaceExecutionEngine's pool.The "Default-Tuning für 500-par.-WF-Topologie" section still carried the old rule of thumb on line 313, producing contradictory guidance within the same document (line 628 already carries the correct measurement from PR #87).
How
Single-line correction in
docs/performance-improvements.md:~30MB pro initialisiertem Runspace. MinRunspaces=128 → ~3.8 GB Idle-RAM. MaxRunspaces=512 → ~15 GB.~1,2–1,4 MB pro initialisiertem Runspace (gemessen 2026-07-30; frühere ~30-MB-Schätzung galt für den Prozess-Spawn-Pfad). MinRunspaces=128 → ~150–180 MB. MaxRunspaces=512 → ~600–720 MB.No code changes — docs only.
Testing
deanden— N/AChecklist
main; no direct commits tomaindocs/adr/— N/AGenerated by nightly docs-sync watchdog (2026-07-31T03:08 UTC). Source PR: #87.
Generated by Claude Code