From 7dcc7b08bb08d14b39ea3bd06f2535b0c87aecd7 Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 31 Jul 2026 03:12:57 +0000 Subject: [PATCH] docs: correct RunspacePool memory rule of thumb after #87 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- docs/performance-improvements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/performance-improvements.md b/docs/performance-improvements.md index 1e0febb..af94ddd 100644 --- a/docs/performance-improvements.md +++ b/docs/performance-improvements.md @@ -310,7 +310,7 @@ Werte aus dem 2026-05-04-Stand der Heuristik plus die aktuelle Live-Zeile separa **Memory-Daumenregel Postgres:** Backend ~10MB pro Connection + `shared_buffers`. Bei `max_connections=600` und `shared_buffers=512MB` zieht Postgres bis zu ~6.5 GB. -**Memory-Daumenregel RunspacePool:** ~30MB pro initialisiertem Runspace. `MinRunspaces=128` → ~3.8 GB Idle-RAM. `MaxRunspaces=512` voll ausgelastet → ~15 GB. +**Memory-Daumenregel RunspacePool:** ~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, nicht den In-Process-Pool — Analyse und Beweis in der WinPSCompat-Session unten). `MinRunspaces=128` → ~150–180 MB Idle-RAM. `MaxRunspaces=512` voll ausgelastet → ~600–720 MB. ### Tests / Verifikation