performance
- Four Bugs That Needed Real Postgres to Exist
A code review found zero bugs. The benchmark found four. Each one required concurrent load against real Postgres to exist.
- Six OOMs and a Connection Pool
A Spring Boot imperative app OOM'd six different ways at 256MB. Each HTTP client swap revealed what was actually eating the heap.
- 1% CPU and 6-Second Latency
A Quarkus reactive app hit 18.8 req/s while CPU idled at 1%. Two stacked bottlenecks — a transaction annotation and a connection pool default — explained the 5x gap with Spring.