LISTEN/NOTIFY performance in PostgreSQL
A NOTIFY in the transaction capped PostgreSQL 18.6 and 19 RC1 at about 3,900 commits per second, with 8 clients or 64. Sending notifications in batches after commit brought 64 clients back to 50,000.
Advice from my high school IT teacher, who wanted me to pick one thing and stick with it. So far I've written CI pipelines, AI platforms, a code search engine and .NET frameworks.
C#, Rust, TypeScript, Python.
A NOTIFY in the transaction capped PostgreSQL 18.6 and 19 RC1 at about 3,900 commits per second, with 8 clients or 64. Sending notifications in batches after commit brought 64 clients back to 50,000.
29 read-only tools for TeamCity. Paste the link to a failed build, get a root-cause analysis built from the actual log lines and test failures.
The tool description is a big part of the interface. If the model can't tell when to call a tool from its description and schema, quality falls apart.
memfd, PE loaders, unlink-after-dlopen. Three operating systems, three different definitions of 'in memory'.
Encrypt a Python package tree, ship it over the network, load it from memory. What works, what doesn't.
16 tools for searching CDN properties, browsing EdgeWorker code, querying DNS, and inspecting network lists. All read-only.