Pipecat, Daily's voice agent framework, merged two Perfloop contributions. The first is chatty I/O, the pattern where something sends way more messages than it needs to: the VAD controller was firing a speech event on every audio frame, when once every 200 ms was the intent, and each one fanned out through the LLM aggregator as a user-speaking frame. One line changed, 17% less CPU on the VAD pipeline. The second is an avoidable copy: the audio volume tracker was rebuilding its 400 ms window from scratch on every chunk. 48.5% fewer bytes copied per update, allocations from 2 to 0.

What are the burning questions you have after watching this Perfloop video tour?

Writing code got cheap, and attention did not. A system stays fast only while someone holds its envelope, and where agents write the code, holding it takes superhuman attention. A freestyle coding agent runs on your attention. What changes the accounting is a harness every change must survive before a person ever looks. perfloop.ai/blog/superhuman-…

Everybody needs Perfloop now.

News flash! First public Perfloop PR not driven by me just landed (link in reply). I'm giving direct access to Perfloop to open source maintainers who care about performance, in return for their feedback. @__Achille__ is driving it on his repos including parquet-go, which we had landed many contributions on already via our OSS tenant. Now he has his own.

See you in October! May the tail be with you.