
@perfloopi
iAccount based inPortugal
About this account
- Account based in
- Portugal
- Connected via
- Web
Account-level information from X, not a live location or the device used for a specific post.
The Performance Machine. Software that stays fast.
United States
Joined April 2026
- Tweets44
- Following20
- Followers220
- Likes58
Perfloop retweeted
Agentic Performance Engineering is out now..
Timestamps:
00:00 The performance problem behind Perfloop
00:39 Why performance work is a battle
03:59 How AI agents raise the stakes
08:55 Quality control at the scale of agentic development
10:34 How Perfloop maps systems and finds opportunities
14:32 Using telemetry to prioritize hot paths
18:13 Perfloop’s open-source performance wins
22:18 How Perfloop measures and verifies improvements
25:11 Common performance patterns and bottlenecks 28:47 The “apex hunt” for bigger architectural gains 30:58 Initiatives and setting high-level performance goals
35:21 Connecting code optimizations to customer impact
39:59 Why independent verification matters
44:36 Choosing the right AI models for each task
49:45 What a harness does in Perfloop
53:59 The possibility of pre-merge performance reviews 57:24 How AI may change the role of performance engineers
63:54 Why performance requires measurement
featuring @tsenart from @perfloop
Perfloop retweeted
Software Engineering is NOT DEAD, but it has changed forever. But how about Performance Engineering?
Can you use Agents to find performance bottleneck, find the root cause and fix it for you?
But how would the approach look like? another prompt?
How do you do the verification?
most importantly how do you avoid Performance engineering SLOP?
Checkout the latest episode on The GeekNarrator with @tsenart who built @perfloop to enable Agentic Performance Engineering. Link in the comments.
Also like, share and repost to make it visible to folks who care about Performance.
Perfloop retweeted
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.
Perfloop retweeted
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-…
🤝
Replying to @TigrisData
@TigrisData is now a @perfloop customer.
Tigris met Perfloop as a pull request: an optimization our system opened in their open source acceleration gateway, tigrisdata/tag, with the evidence attached.
@ovaistariq read it and merged it, then asked on X: "How do I get access :)". He signed up the next evening.
Within a week he had connected repos himself and brought his cofounders in. In the two weeks since, Tigris has merged sixteen more of Perfloop's pull requests, four of them in tag: github.com/tigrisdata/tag
Perfloop retweeted
Just got some nice perf work stream done with @perfloop and Claude working together github.com/tigrisdata/tag/pu…
Perfloop retweeted
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.
We’re all about chop chop.
I'm that boss telling my agents to chop chop.
Many people have had the failure mode of over-engineering and defending against an ever larger bucket of corner cases.
And boy oh boy, isn't GPT 5.6 Sol mimicking that behavior.
That's one of my next challenges: how to keep automated review loops but cut them short at the right point of pragmatism.
Perfloop retweeted
See you in October! May the tail be with you.
We can't wait to learn about a software loop that does the full arc of performance engineering from @tsenart at this year's #P99CONF. Don't miss your chance to learn what this looks like for teams running performance-sensitive workloads: ow.ly/P68h50ZnQHc
#ScyllaDB
❤️
Another repo under Perfloop’s managed portfolio: Zoekt, the engine powering Sourcegraph’s code search. app.perfloop.ai/t/oss/case_1…
👾👾👾
Another monster optimization on parquet-go landed by @perfloop
app.perfloop.ai/t/oss/case_k…
Machine speed
Perfloop just merged its first PR into a second repo: RoaringBitmap/roaring.
It rewrote a bit-sliced batch-equality query to run directly over the bitplanes instead of scanning column by column. In our benchmark harness: about 30x faster, ~70% less memory, no behavior change.
Three merges in two weeks now, across parquet-go and roaring, both built by people who care deeply about performance. So why is there still this much to find? Performance isn't just skill-bound, it's attention-bound. No fixed amount of attention covers a surface this large, and it keeps growing. That's the problem, not the people.
Code is increasingly written at machine speed. Keeping it fast has to happen at machine speed too.














