Next: Profiling Reference, Previous: Profiling Overview, Up: Profiling
One reason for using the profile class is that it takes care of
profile file naming and placement. Applications can get the profile
file location using Profile::profile_file_path_get, but this is
rarely necessary. Applications that want this naming and placement but
don't want to use the profile class for actually reading and writing
files can use profile_path_make or profile_path_make_opts.
A profile file name is constructed as follows: PROFILE_DIR/NAME/BENCHMARK_PREFIX-VERSION.pro
PROFILE_DIR is the value of the profile_dir RTI.
NAME is the value of the name argument of the
Profile constructor or init function.
BENCHMARK_PREFIX is either the first two components of the
benchmark_id RTI, the entire benchmark_id, or,
if benchmark_id is not set, the name of the benchmark executable
file. See the per option for the mode argument.
VERSION is the value of the version argument of the
Profile constructor or init function.