Skip to content

docs: sync after #87 (RunspacePool memory rule of thumb correction) #90

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Sev7eNup merged 1 commit into from
Jul 31, 2026
Merged

docs: sync after #87 (RunspacePool memory rule of thumb correction) #90

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/performance-improvements.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Loading