Skip to content

Avoid pinning CPU to the last core #318

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

Merged
merged 1 commit into from
Aug 15, 2024
Merged

Avoid pinning CPU to the last core #318

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
4 changes: 3 additions & 1 deletion run_benchmarks.rb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -253,7 +253,9 @@ def run_benchmarks(ruby:, ruby_description:, categories:, name_filters:, out_pat
# Pin the process to one given core to improve caching and reduce variance on CRuby
# Other Rubies need to use multiple cores, e.g., for JIT threads
if ruby_description.start_with?('ruby ') && !no_pinning
cmd += ["taskset", "-c", "#{Etc.nprocessors - 1}"]
# The last few cores of Intel CPU may be slow E-Cores, so avoid using the last one.
cpu = [(Etc.nprocessors / 2) - 1, 0].max
cmd += ["taskset", "-c", "#{cpu}"]
end
end

Expand Down