Low-Overhead Statistical Profiling with Oprofile

Sometimes System Administrators need to determine where applications spend most of their time, in order to tune their systems better. The traditional method, when the source code for the application and gcc are available, is just to recompile the application with the – pg flag and to use gprof to profile it. Other than the inconvenience of the recompilation process, the solution is pretty straightforward. But what happens when you don’t have the source code for the application? And what if you’d like to profile the system as a whole? That’s when oprofile comes in handy.


  1. 2005-06-25 8:33 pm
  2. 2005-06-25 11:03 pm
  3. 2005-06-25 11:09 pm
  4. 2005-06-26 3:01 am
  5. 2005-06-26 4:35 am
  6. 2005-06-26 5:11 am
  7. 2005-06-26 10:36 pm
  8. 2005-06-27 8:11 am