Platform guides
The Tuning Model covers PostgreSQL GUCs that respond predictably to pgbent workloads. Platform guides cover the layer underneath: OS I/O class, device read-ahead, NVMe firmware defaults, and how the server process is started. Those knobs are easy to leave at desktop or SAN defaults and then blame on Postgres.
Think of vendor NAS runbooks (EMC and friends) that publish database-oriented storage settings — except here the evidence is public, measured on named hosts, with scripts you can re-run. Isolation write-ups that feed this section live under Studies.
Start here
- Linux standard OS tuning — what
pgbent_tuneapplies after every boot, and why - NVIDIA DGX Spark platform review — court: coalescing + mixed-core SELECT grid, power (
spark_hwmon/ spbm), NIC EEE / ASPM - macOS LaunchAgent I/O class — Homebrew
brew servicesutility clamp
The full ARM miss isolation case (select-scatter-64, Relations, court vs twilight vs Abbey) is the ARM random read vs x86 study.