harfbuzz/perf
Garret Rieger d1bf6c0c26 [subset] only preprocess in benchmark when experimental api is enabled. 2022-10-17 20:14:02 +00:00
..
fonts
texts [benchmark-shape] Remove a few tests 2022-06-05 02:04:02 -06:00
Makefile.am
README.md [perf] Update README 2022-06-30 14:09:09 -06:00
benchmark-font.cc [benchmark-font] Disable quadratic callback 2022-06-27 12:10:16 -06:00
benchmark-map.cc
benchmark-ot.cc
benchmark-set.cc [benchmark-set] Another Pause/Resume 2022-05-30 05:54:20 -06:00
benchmark-shape.cc [benchmark-shape,hb-shape-threads] Fix argument parsing order 2022-06-05 06:53:42 -06:00
benchmark-subset.cc [subset] only preprocess in benchmark when experimental api is enabled. 2022-10-17 20:14:02 +00:00
meson.build
run.sh

README.md

Building and Running

Benchmarks are implemented using Google Benchmark.

To build the benchmarks in this directory you need to set the benchmark option while configuring the build with meson:

meson build -Dbenchmark=enabled --buildtype=release

or:

meson build -Dbenchmark=enabled --buildtype=debugoptimized

Then build a specific benchmark binaries with ninja:

ninja -Cbuild perf/benchmark-set

or just build the whole project:

ninja -Cbuild

Finally, to run one of the benchmarks:

./build/perf/benchmark-set

It's possible to filter the benchmarks being run and customize the output via flags to the benchmark binary. See the Google Benchmark User Guide for more details.

Profiling

Configure the build to include debug information for profiling:

CXXFLAGS="-fno-omit-frame-pointer" meson --reconfigure build -Dbenchmark=enabled --buildtype=debug
ninja -Cbuild

Then run the benchmark with perf:

perf record -g build/perf/benchmark-subset --benchmark_filter="BM_subset_codepoints/subset_notocjk/100000" --benchmark_repetitions=5

You probably want to filter to a specific benchmark of interest and set the number of repititions high enough to get a good sampling of profile data.

Finally view the profile with:

perf report