PgBouncer: from 45K to 210K queries per second
Eight PgBouncer processes reached 210K queries per second with the same 128-connection pool. PostgreSQL CPU rose from 22% to 97%.
Notes from my software experiments. What I tried, what happened, and the code to run it yourself.
4 notes in the notebook
Eight PgBouncer processes reached 210K queries per second with the same 128-connection pool. PostgreSQL CPU rose from 22% to 97%.
At 101 million vectors, TurboVec's 4-bit index used 37.4 GB and reached 0.914 recall@10. Median search time was 5.67 seconds.
Five ways to load the same million-row CSV. Typed COPY took 3.91 seconds; the 1.29-second result used a text-only staging table.
Streaming 2 million JSONL records kept peak memory around 25 MB. Loading the full JSON array used 3.5 to 7.4 GB, depending on the parser.