ProfilingWesnoth: Difference between revisions
From The Battle for Wesnoth Wiki
Pentarctagon (talk | contribs) No edit summary |
Pentarctagon (talk | contribs) |
||
| Line 9: | Line 9: | ||
# Run the executable and have it do any task(s) as needed to get relevant profiling information. | # Run the executable and have it do any task(s) as needed to get relevant profiling information. | ||
# Generate the human-readable profiling output using the command <code>google-pprof <executable> <profiling info> > prof.txt</code> for a text file, or <code>google-pprof -gif <executable> <profiling info> > prof.gif</code> for a viewable gif image. | # Generate the human-readable profiling output using the command <code>google-pprof <executable> <profiling info> > prof.txt</code> for a text file, or <code>google-pprof -gif <executable> <profiling info> > prof.gif</code> for a viewable gif image. | ||
Unfortunately, the output, whether graphical or text, doesn't provide any labels for what the values mean. For the text output, the columns are: | |||
# The number of profiling samples in this function | |||
# The percentage of profiling samples in this function | |||
# The percentage of profiling samples in the functions printed so far | |||
# The number of profiling samples in this function and its callees | |||
# The percentage of profiling samples in this function and its callees | |||
# The function name | |||
For the graphical output, each square will contain: | |||
# The namespace/class/method profiled each on a separate line | |||
# The number of profiling samples in this function | |||
# The percentage of profiling samples in this function (in parenthesis) | |||
# The number of profiling samples in this function and its callees | |||
# The percentage of profiling samples in this function and its callees (in parenthesis) | |||
=== perf === | === perf === | ||
Revision as of 04:30, 9 June 2021
Linux
When using either scons or cmake to build, there are four options available for profiling which are listed below. For cmake use -DPROFILER=<name>, for scons use profiler=<name>.
gperftools
To use gperftools:
- Install the packages
google-perftools(needed later for running google-pprof) andlibgoogle-perftools-dev(needed in order to use the -lprofiler linker option). - In a terminal, export the
CPUPROFILEvariable, such asexport CPUPROFILE=./wesnoth-prof. - Build any executable while setting either
-DPROFILER=gperftools(cmake) orprofiler=gperftools(scons). - Run the executable and have it do any task(s) as needed to get relevant profiling information.
- Generate the human-readable profiling output using the command
google-pprof <executable> <profiling info> > prof.txtfor a text file, orgoogle-pprof -gif <executable> <profiling info> > prof.giffor a viewable gif image.
Unfortunately, the output, whether graphical or text, doesn't provide any labels for what the values mean. For the text output, the columns are:
- The number of profiling samples in this function
- The percentage of profiling samples in this function
- The percentage of profiling samples in the functions printed so far
- The number of profiling samples in this function and its callees
- The percentage of profiling samples in this function and its callees
- The function name
For the graphical output, each square will contain:
- The namespace/class/method profiled each on a separate line
- The number of profiling samples in this function
- The percentage of profiling samples in this function (in parenthesis)
- The number of profiling samples in this function and its callees
- The percentage of profiling samples in this function and its callees (in parenthesis)
perf
gcov
gprof
This page was last edited on 9 June 2021, at 04:30.