From 33b37c5dab495c733f5a0beda7f53872bb7776e9 Mon Sep 17 00:00:00 2001 From: Ashton Larkin <42042756+adlarkin@users.noreply.github.com> Date: Wed, 14 Apr 2021 16:31:21 -0400 Subject: [PATCH] Update benchmark comparison instructions (#766) (#766) Signed-off-by: Ashton Larkin --- test/benchmark/README.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/test/benchmark/README.md b/test/benchmark/README.md index 2fb4934c99..a5f7f79b8a 100644 --- a/test/benchmark/README.md +++ b/test/benchmark/README.md @@ -14,24 +14,24 @@ Given a set of changes to the codebase, it is often useful to see the difference in performance. -Once two (or more) benchmarks have been executed, compare the results with: +Once two (or more) benchmarks have been executed, compare the results by downloading the [benchmark tools](https://github.com/google/benchmark/tree/master/tools), and then run the following command: - ``` - # From the build folder - ../test/gbenchmark/tools/compare.py benchmarks baseline.json contender.json - ``` +``` +# From the downloaded "tools" folder +./compare.py benchmarks baseline.json contender.json +``` ### CPU Scaling Warnings Note: If you receive warnings about CPU scaling, you can change the CPU governor with: - ``` - sudo cpupower frequency-set --governor performance - ``` +``` +sudo cpupower frequency-set --governor performance +``` The previous setting can be restored with: - ``` - sudo cpupower frequency-set --governor powersave - ``` +``` +sudo cpupower frequency-set --governor powersave +```