Start here
Node.js40 MB an hour: the Node memory leak hiding behind setMaxListeners(0)
A postmortem of a slow leak in a Node ingest service: how two heap snapshots, one retainer chain and a silenced warning led us to the bug.
Read the storyA group engineering blog
We broke prod so you can read about it
Idempotency keys, jittered retries, a memory leak hiding behind setMaxListeners(0). Bring coffee, we brought the stack traces.
Latest posts
Browse by topic
- Postgres4Indexes, query plans, migrations and the locks behind them, written from the point of view of the team that owns the database.Browse
- Node.js3The Node runtime in production: memory, the event loop, testing and the tooling around TypeScript services.Browse
- Reliability3Retries, idempotency, safe deploys and the habits that keep a service up when its dependencies are not.Browse
- Performance3Finding where the time and memory go, with measurements first and opinions second.Browse
- Go2Go services and workers: profiling with pprof, concurrency, retries and small helpers worth copying.Browse
- Testing2Tests that catch real bugs: time, randomness, failure paths and the cases that only break in production.Browse