platform_bionic/benchmarks/linker_relocation
Elliott Hughes 68ae6ad12e Changes for #inclusivefixit.
Test: treehugger
Change-Id: I7ff0496c5c2792a41781e74634247f55b0548213
2020-07-21 16:34:58 -07:00
..
gen Add a linker relocation benchmark 2020-01-14 13:12:56 -08:00
include Add a linker relocation benchmark 2020-01-14 13:12:56 -08:00
regen Changes for #inclusivefixit. 2020-07-21 16:34:58 -07:00
.gitignore Add a linker relocation benchmark 2020-01-14 13:12:56 -08:00
Android.bp Add a liblog dependency 2020-01-15 19:59:04 -08:00
gen_bench.sh Add a linker relocation benchmark 2020-01-14 13:12:56 -08:00
linker_reloc_bench.cpp Add a linker relocation benchmark 2020-01-14 13:12:56 -08:00
README.md Add a linker relocation benchmark 2020-01-14 13:12:56 -08:00
run_bench_with_ninja.sh Add a linker relocation benchmark 2020-01-14 13:12:56 -08:00

Dynamic Linker Relocation Benchmark

This benchmark measures the time spent in the dynamic linker to load a large set of shared objects with many symbols and relocations. It mimics the work involved in loading a fixed version of libandroid_servers.so.

Running the benchmark

To run the benchmark, build the linker-reloc-bench target, sync data, and run the benchmark from /data/benchmarktest[64]/linker-reloc-bench.

There is also a run_bench_with_ninja.sh script that uses the gen_bench.py --ninja mode to generate a benchmark. It's useful for experimentation. The --cc and --linker flags allow swapping out different static and dynamic linkers.

Regenerating the synthetic benchmark

regen/dump_relocs.py scans an ELF file and its dependencies, outputting a JSON dump, then regen/gen_bench.py processes the JSON file into benchmark code. gen_bench.py has two modes:

  • (default) generate Android.bp and source files
  • with --ninja: generate a build.ninja instead, and build a set of ELF file outputs