Do you like to read about performance investigations? Me too!
I'm fanatical about performance. Computers and software must be fast! Performance investigations are one of my favorite parts of how systems work because they rarely turn out to be what you expect at first.
Just imagine. You are working on another feature. You squeezed the last details out of your project manager, thought it through from every possible angle, and wrote the initial code without O(n!) algorithms. You deploy your changes to staging, run your first tests, open Grafana expecting to see the graphs you anticipated, and...
Does it sound familiar? You know how it ends, right? I have been in situations like this many times.
Although these situations can be stressful, this is still one of my favorite parts of the profession. I have always had my nose buried in performance posts and have always been happy to see another one in my RSS feed - whether from Brendan Gregg, the ClickHouse Engineering Blog, the Percona Database Performance Blog, or many others.
At some point, I thought, "hey, I also have a big collection of such stories. They might be interesting to other people too".
So I have decided to start writing performance hunting stories from my own experience: what I saw, what I tried, what didn't work, and what the problem actually turned out to be.
Interested? More performance hunting stories are coming here and at https://t.co/TRTRugEThc.
And there is a "traditional" sequel to this AI-native smartphone research: we just achieved a full Android kernel exploit, gaining root on the Doubao Phone with CVE-2026-21385 😎⚡️
“Never give in. Never give in. Never, never, never, never-in nothing, great or small, large or petty-never give in, except to convictions of honour and good sense. Never yield to force. Never yield to the apparently overwhelming might of the enemy.”
-Winston Churchill