Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update benchmark comparison instructions #766

Merged
merged 1 commit into from
Apr 14, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 11 additions & 11 deletions test/benchmark/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
```