Making Postgres 42,000x slower because I am unemployed
9 months ago
- #PostgreSQL
- #Database Optimization
- #Performance Tuning
- The article explores how to intentionally slow down PostgreSQL performance by tweaking configuration parameters in postgresql.conf.
- Key methods include reducing shared_buffers to force disk reads, aggressively configuring autovacuum to run frequently, and optimizing WAL settings to maximize writes.
- The author also disables index usage by setting random_page_cost and cpu_index_tuple_cost to extremely high values.
- Finally, I/O is bottlenecked into a single thread using io_method and io_workers settings.
- The result is a PostgreSQL instance that is 42,000 times slower than its default configuration.
- The article includes a full list of the 32 parameters modified to achieve this extreme slowdown.