postgres@jusdb:~$ jusdb tune --explain
PostgreSQL Config Optimizer
A workload-tuned postgresql.conf in seconds - RAM-budgeted shared_buffers + work_mem math, pooler-aware connection sizing, and a per-parameter rationale for every line it writes.
Server profile
Toggles max_connections sizing for backend pool vs direct app connections.
Memory footprint
Bar shows realistic steady-state allocation: ~2 autovacuum workers active, ~40% of max_connections backends running with workload-typical work_mem ops. Worst-case pill (top-right) is the OOM ceiling - every backend peaks every buffer simultaneously, which essentially never happens but bounds the risk. PG keeps shared_buffers small (25%) so the headroom serves as OS page cache.
Disk footprint (beyond user data)
WAL is the biggest disk consumer beyond user data. Provision your pg_wal volume for max_wal_size + wal_keep_size + 2× daily WAL so an unexpected slot pause doesn't fill the disk.