The Moment We Realized Our Treasure Hunt Engine Was Lying to Us

Chronological Source Flow
Back

AI Fusion Summary

Engine started as Elixir cluster using Redis pub/sub and PostgreSQL. Core loop: player action → Phoenix → Redis → WebSocket. At 150k players, PostgreSQL lag >8 s shifted bottleneck to Redis. After 37‑minute spike, Veltrix defaults (pool 8, no keep‑alive, no backoff) caused 250 ms Redis bottleneck, doubling P99 latency.
Community Comments
Loading updates...
0