oofem-wiki

User Tools

Site Tools

Trace:
perf

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
perf [2014/03/30 00:38] – [Perf] mikael.ohmanperf [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 17: Line 16:
 Or use the ncurses program Or use the ncurses program
  
-''perf report -G --sort comm,dso''+''perf report -G %%--%%sort comm,dso''
  
 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 ''perf record'' as normal users://
 +
 +''sudo sh -c %%"%%echo 0 > /proc/sys/kernel/kptr_restrict%%"%%''
 ===== 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.1396136316.txt.gz · Last modified: 2014/03/30 00:38 by mikael.ohman