# Tuned config for the throwaway bench Postgres instance. # Pinned to this machine: Apple Silicon, 14 cores, 36GB RAM (`sysctl hw.physicalcpu hw.memsize`). # Appended verbatim to postgresql.conf by harness/pgctl.py after initdb. # Port and unix_socket_directories are set separately per-run (harness picks a free port). # # Rationale: this instance never sees concurrent unrelated workloads and is # rebuilt per run, so we trade durability for throughput/build-speed and size # memory against the whole machine, not a shared server's fair share. shared_buffers = 8GB effective_cache_size = 24GB maintenance_work_mem = 2GB work_mem = 256MB max_worker_processes = 14 max_parallel_workers = 14 max_parallel_maintenance_workers = 7 # Bulk build/insert speed; this data is 100% reproducible from the harness, never # worth protecting with fsync durability. fsync = off synchronous_commit = off full_page_writes = off wal_level = minimal max_wal_senders = 0 wal_buffers = 64MB min_wal_size = 4GB max_wal_size = 16GB checkpoint_timeout = 30min checkpoint_completion_target = 0.9 # Enough headroom for 8-connection concurrency benchmarks + monitor connections. max_connections = 64 # Deterministic, reviewable query plans. random_page_cost = 1.1 # effective_io_concurrency left at its default (0): macOS lacks posix_fadvise(), # so any nonzero value fails startup here. On the Linux over-RAM runbook target, # set this to e.g. 200 for the SSD-backed case. logging_collector = off log_min_messages = warning # The harness controls VACUUM explicitly (the churn workload measures its # cost/recovery directly). Autovacuum firing mid-sweep would silently add # noise to latency measurements and contend with our own VACUUM calls for # the same table (observed: a manual VACUUM stuck behind/alongside a # concurrent autovacuum worker took minutes on a 50k-row table instead of # seconds). Off entirely for this throwaway, short-lived instance. autovacuum = off