Lines Matching full:benchmark

4 Fruit contains some code to benchmark various metrics (e.g. performance, compile time, executable s…
7 ### Benchmark suites
13 $ ~/projects/fruit/extras/benchmark/run_benchmarks.py \
14     --continue-benchmark=true \
15     --benchmark-definition ~/projects/fruit/extras/benchmark/suites/fruit_full.yml
18     --fruit-benchmark-sources-dir ~/projects/fruit \
22 Once the benchmark run completes, you can format the results using some pre-defined tables, see the…
24 The following benchmark suites are defined:
33 …`fruit_full.yml`. This is a quick benchmark that can used during development of performance optimi…
36 * `boost_di`: unlike the others, this benchmark suite exercises the Boost.DI library (still in boos…
39 ### Benchmark tables
42 benchmark results generated using `run_benchmarks.py`.
44 Note that there *isn't* a 1:1 mapping between benchmark suites and benchmark tables; the same table…
45 used with multiple benchmark suites (for example, a full suite and a quick variant that only has a …
53 $ ~/projects/fruit/extras/benchmark/format_bench_results.py \
54     --benchmark-results ~/fruit_bench_results.txt \
55     --benchmark-tables-definition ~/projects/fruit/extras/benchmark/tables/fruit_wiki.yml
58 It's also possible to compare two benchmark results (for example, when running the same benchmarks …
62 $ ~/projects/fruit/extras/benchmark/format_bench_results.py \
63     --benchmark-results ~/fruit_bench_results_after.txt \
64     --benchmark-tables-definition ~/projects/fruit/extras/benchmark/tables/fruit_wiki.yml \
65     --baseline-benchmark-results ~/fruit_bench_results_before.txt
77 benchmark run). This is how you can do that:
87 $ extras/benchmark/generate_benchmark.py \