perf
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
perf [2014/03/29 19:21] – [Perf] mikael.ohman | perf [2014/08/22 00:11] (current) – [Perf] mikael.ohman | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Measuring performance ====== | ====== Measuring performance ====== | ||
In general, to obtain useful information from binaries, certain compile flags should be used. | In general, to obtain useful information from binaries, certain compile flags should be used. | ||
- | |||
===== Perf ===== | ===== Perf ===== | ||
Line 11: | Line 10: | ||
which will generate a perf.data file. | which will generate a perf.data file. | ||
- | Then you can visualize the results in several ways. A good, simple to understand method is to use gprof2dot | + | Then you can visualize the results in several ways. A good, simple to understand method is to use [[http:// |
- | '' | + | '' |
+ | |||
+ | Or use the ncurses program | ||
+ | |||
+ | '' | ||
Perf has very small overhead, but only does statistical sampling. | Perf has very small overhead, but only does statistical sampling. | ||
+ | |||
+ | |||
+ | //Users of perf will likely first need to turn off the restrictions before they are able to run '' | ||
+ | |||
+ | '' | ||
===== Callgrind ===== | ===== Callgrind ===== | ||
Callgrind is a tool in valgrind, and should only be used on medium. This has a huge overhead, so expect OOFEM to run over a hundred times slower through valgrind. | Callgrind is a tool in valgrind, and should only be used on medium. This has a huge overhead, so expect OOFEM to run over a hundred times slower through valgrind. |
perf.1396117265.txt.gz · Last modified: 2014/03/29 19:21 by mikael.ohman