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.

Sign up for GitHub

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

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

Merged
merged 1 commit into from
Jan 10, 2024
Merged

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 2 additions & 4 deletions docs/reducing_variance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
your system while benchmarking.

See [Reducing Variance](reducing_variance.md) for more information.

Exactly how to do this depends on the Linux distribution,
desktop environment, and installed programs. Specific details are a moving
target, so we will not attempt to exhaustively document them here.
Expand Down Expand Up @@ -67,7 +65,7 @@ program.
Reducing sources of variance is OS and architecture dependent, which is one
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:

1. Use the performance governor as [discussed
Expand All @@ -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
your web browser, desktop environment, etc.
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.

Further resources on this topic:
Expand Down
Loading