Lines Matching refs:benchmark

9 $ compare_bench.py <old-benchmark> <new-benchmark> [benchmark options]...
12 …benchmark>` and `<new-benchmark>` either specify a benchmark executable file, or a JSON output fil…
14 `[benchmark options]` will be passed to the benchmarks invocations. They can be anything that binar…
39 When a benchmark executable is run, the raw output from the benchmark is printed in real time to st…
85 $ compare.py benchmarks <benchmark_baseline> <benchmark_contender> [benchmark options]...
87 …benchmark executable file, or a JSON output file. The type of the input file is automatically dete…
89 `[benchmark options]` will be passed to the benchmarks invocations. They can be anything that binar…
141 …benchmark from the first run it looks for the benchmark with exactly the same name in the second r…
144 2. Compare two different filters of one benchmark
148 $ compare.py filters <benchmark> <filter_baseline> <filter_contender> [benchmark options]...
150 …benchmark>` either specify a benchmark executable file, or a JSON output file. The type of the inp…
152 …ilters that you would pass to the `[--benchmark_filter=<regex>]` parameter of the benchmark binary.
154 `[benchmark options]` will be passed to the benchmarks invocations. They can be anything that binar…
191 …benchmark, and before doing the diff. And to make the diff work, the matches are replaced with som…
194 3. Compare filter one from benchmark one to filter two from benchmark two:
198 …nchmark_baseline> <filter_baseline> <benchmark_contender> <filter_contender> [benchmark options]...
201 …benchmark executable file, or a JSON output file. The type of the input file is automatically dete…
203 …ilters that you would pass to the `[--benchmark_filter=<regex>]` parameter of the benchmark binary.
205 `[benchmark options]` will be passed to the benchmarks invocations. They can be anything that binar…
241 This is a mix of the previous two modes, two (potentially different) benchmark binaries are run, an…