All posts
Data Platform

The Noisy Neighbour, Measured: Key Lookups in Postgres and DynamoDB While a Report Runs

By

November 9, 2026

6 min read

Key lookups in Postgres went from 0.16 ms to 9.75 ms, about 60 times slower, while four reporting queries ran on the same 2-vCPU instance. In DynamoDB, lookups stayed at 2.5 ms during a parallel scan of the same table. And what a jump from 10 to 1,000 concurrent clients did to each.

Benchmark
Postgres Performance
DynamoDB
Postgres0.16 ms9.8 msDynamoDB2.7 ms2.5 ms

Alone

During a report

Median key lookup, alone and while reporting queries run against the same database (log scale). Our measurements, November 2026.

The data
AloneDuring a report
Postgres0.16 ms9.8 ms
DynamoDB2.7 ms2.5 ms

This is the strongest case for keeping analytics off your primary database, or for DynamoDB's isolation. The full report has p99s, the spike test second by second, and the usual fixes: read replicas, exports and separate analytics stores.

Reports slowing down your app?

We'll find which queries collide and where they should run instead. 30 minutes, free.

hoolco Monthly Review

Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.

As of November 9, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.