dolysis/benchmark
3
0
Fork 0
mirror of https://github.com/google/benchmark.git synced 2024-11-28 05:44:40 +00:00
Code Issues Packages Projects Releases Wiki Activity

Docs: reducing_variance.md: proofreading, fix typos (#1736)

Browse source
This commit is contained in:
Roman Lebedev 2024-01-10 12:37:39 +03:00 committed by GitHub
parent 882f6f5ae0
commit ea71a14891
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/reducing_variance.md
View file

@ -14,8 +14,6 @@ you might want to disable the CPU frequency scaling while running the
benchmark, as well as consider other ways to stabilize the performance of benchmark, as well as consider other ways to stabilize the performance of
your system while benchmarking. your system while benchmarking.
See [Reducing Variance](reducing_variance.md) for more information.
Exactly how to do this depends on the Linux distribution, Exactly how to do this depends on the Linux distribution,
desktop environment, and installed programs. Specific details are a moving desktop environment, and installed programs. Specific details are a moving
target, so we will not attempt to exhaustively document them here. target, so we will not attempt to exhaustively document them here.
@ -67,7 +65,7 @@ program.
Reducing sources of variance is OS and architecture dependent, which is one Reducing sources of variance is OS and architecture dependent, which is one
reason some companies maintain machines dedicated to performance testing. reason some companies maintain machines dedicated to performance testing.
Some of the easier and and effective ways of reducing variance on a typical Some of the easier and effective ways of reducing variance on a typical
Linux workstation are: Linux workstation are:
1. Use the performance governor as [discussed 1. Use the performance governor as [discussed
@ -89,7 +87,7 @@ above](user_guide#disabling-cpu-frequency-scaling).
4. Close other programs that do non-trivial things based on timers, such as 4. Close other programs that do non-trivial things based on timers, such as
your web browser, desktop environment, etc. your web browser, desktop environment, etc.
5. Reduce the working set of your benchmark to fit within the L1 cache, but 5. Reduce the working set of your benchmark to fit within the L1 cache, but
do be aware that this may lead you to optimize for an unrelistic do be aware that this may lead you to optimize for an unrealistic
situation. situation.
Further resources on this topic: Further resources on this topic: