Beyond Stack Sampling: C++ Profilers

by

First:

Time sampling profilers are more robust than CPU sampling profilers. I’m not extremely familiar with Windows development tools so I can’t say which ones are which. Most profilers are CPU sampling.

A CPU sampling profiler grabs a stack trace every N instructions.
This technique will reveal portions of your code that are CPU bound. Which is awesome if that is the bottle neck in your application. Not so great if your application threads spend most of their time fighting over a mutex.

A time sampling profiler grabs a stack trace every N microseconds.
This technique will zero in on “slow” code. Whether the cause is CPU bound, blocking IO bound, mutex bound, or cache thrashing sections of code. In short what ever piece of code is slowing your application will standout.

So use a time sampling profiler if at all possible especially when profiling threaded code.

Second:

Sampling profilers generate gobs of data. The data is extremely useful, but there is often too much to be easily useful. A profile data visualizer helps tremendously here. The best tool I’ve found for profile data visualization is gprof2dot. Don’t let the name fool you, it handles all kinds of sampling profiler output (AQtime, Sleepy, XPerf, etc). Once the visualization has pointed out the offending function(s), jump back to the raw profile data to get better hints on what the real cause is.

The gprof2dot tool generates a dot graph description that you then feed into a graphviz tool. The output is basically a callgraph with functions color coded by their impact on the application.
alt text

A few hints to get gprof2dot to generate nice output.

  • I use a --skew of 0.001 on my graphs so I can easily see the hot code paths. Otherwise the int main() dominates the graph.
  • If you’re doing anything crazy with C++ templates you’ll probably want to add --strip. This is especially true with Boost.
  • I use OProfile to generate my sampling data. To get good output I need configure it to load the debug symbols from my 3rd party and system libraries. Be sure to do the same, otherwise you’ll see that CRT is taking 20% of your application’s time when what’s really going on is malloc is trashing the heap and eating up 15%.

More Related Contents:

  1. Measuring execution time of a function in C++
  2. Decompile qt exe [closed]
  3. Why does C++ code for testing the Collatz conjecture run faster than hand-written assembly?
  4. Meaning of acronym SSO in the context of std::string
  5. Position of least significant bit that is set
  6. Is “for(;;)” faster than “while (true)”? If not, why do people use it?
  7. Qt Linker Error: “undefined reference to vtable” [duplicate]
  8. How to link opencv in QtCreator and use Qt library
  9. Deoptimizing a program for the pipeline in Intel Sandybridge-family CPUs
  10. How to build Qt for Visual Studio 2010
  11. How to redirect qDebug, qWarning, qCritical etc output?
  12. Different floating point result with optimization enabled – compiler bug?
  13. Qt: resizing a QLabel containing a QPixmap while keeping its aspect ratio
  14. cv::Mat to QImage and back
  15. How to read file content into istringstream?
  16. What kinds of optimizations does ‘volatile’ prevent in C++?
  17. what does __declspec(dllimport) really mean?
  18. How do I create a simple Qt console application in C++?
  19. Fastest implementation of sine, cosine and square root in C++ (doesn’t need to be much accurate)
  20. how to restart my own qt application?
  21. Should I unify two similar kernels with an ‘if’ statement, risking performance loss?
  22. Ncurses and Qt Interoperability
  23. Get sum of values stored in __m256d with SSE/AVX
  24. Is a logical right shift by a power of 2 faster in AVR?
  25. QDialog exec() and getting result value
  26. How do I make an image resize to scale in Qt?
  27. how to add zlib to an existing qt installation
  28. Qt macro keywords cause name collisions
  29. Optimizations for pow() with const non-integer exponent?
  30. Two colours text in QPushButton

Leave a Comment