Making Postgres 42,000x slower because I am unemployed

This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).

A developer systematically degrades PostgreSQL performance by 42,000x through configuration changes alone, exploring how various postgresql.conf parameters affect database speed. The experiment reduces buffer cache size, forces excessive autovacuum operations, maximizes WAL overhead, disables index usage through cost manipulation, and bottlenecks I/O to a single thread. Starting from 7,082 TPS with default settings, the final configuration achieves less than 0.1 TPS with only 11 successful transactions in 120 seconds across 100 connections.

14m read timeFrom byteofdev.com
Post cover image
Table of contents
The ParametersCaching? Nah…Making Postgres Perform As Background Work Much As PossibleTurning Postgres into Brandon SandersonEssentially Deleting IndexesForcing I/O Into One ThreadFinal Thoughts
9 Comments

Sort: