In my previous post I've presented a list of bugs reported by famous MySQL developers, DBAs, users and support engineers who used oprofile to find the problem or root cause of the problem they studied. I assume that some of my readers would like to follow their steps and try to use this tool while working on MySQL performance problems. Bug reports I mentioned contain outputs and, rarely, just some commands used. That's why I decided to write a kind of a basic "Howto" document. The tool does have a detailed enough manual, but few basic steps for quick use of oprofile to study MySQL-related problems should still help. At least I had always considered …[Read more]
Users had to identify the reasons for MySQL performance problems
somehow well before famous Performance Schema appeared in MySQL 5.5.3,
and even before Domas invented his Poor Man's Profiler. Poor users had
to use some OS-level tools, and among these tools the most
important one was, probably, oprofile.
oprofile is a system-wide statistical profiling tool for Linux available since 2001 and 2.4.x kernels. It was applied to MySQL for many …