Skip to content

Clarify CPU frequency stability guidance#2210

Open
Haihan-Jiang wants to merge 3 commits into
google:mainfrom
Haihan-Jiang:codex/benchmark-verify-cpu-frequency-settings
Open

Clarify CPU frequency stability guidance#2210
Haihan-Jiang wants to merge 3 commits into
google:mainfrom
Haihan-Jiang:codex/benchmark-verify-cpu-frequency-settings

Conversation

@Haihan-Jiang

Copy link
Copy Markdown
Contributor

Summary:

  • soften the CPU governor guidance from a guarantee to a usual variance reduction
  • call out that boost, SMT/Hyperthreading, firmware, and kernel behavior can still affect observed frequency
  • suggest monitoring per-CPU frequency during sensitive benchmark runs

Fixes #1686.

Test:

  • git diff --check

Comment thread docs/reducing_variance.md Outdated
@Haihan-Jiang

Copy link
Copy Markdown
Contributor Author

Pushed 5e5d81a to remove the duplicated sentence here; the lower variance section now remains the canonical place for that guidance.

@Haihan-Jiang Haihan-Jiang force-pushed the codex/benchmark-verify-cpu-frequency-settings branch from 1c694fb to bbca5a7 Compare June 14, 2026 10:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Reducing variance doc incorrectly recommends disabling hyper threading AND pinning CPU frequency scaling?

2 participants