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

context1: set cpu affinity for more stable benchmark results #80

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

citizen4yu
Copy link

"Pipe-based Context Switching" sometimes parent and child process will
run on the same CPU, run on the same CPU score higher than different
CPU.

Signed-off-by: citizen4 [email protected]

"Pipe-based Context Switching" sometimes parent and child process will
run on the same CPU, run on the same CPU score higher than different
CPU.

Signed-off-by: citizen4 <[email protected]>
@gstrauss
Copy link
Collaborator

Do you think we should force them onto the same CPU, or should we force them onto different CPUs? Not hyperthread? Difference cores? Different processors?

On a many-cored system, the likelihood of being scheduled on the same CPU goes down, so I think that we might want to force processes onto separate CPU cores, though perhaps on the same processor, as a compromise and to preserve some memory locality rather than potentially suffering NUMA penalties/disparities.

@gstrauss gstrauss changed the title context1: fix issue #79 context1: set cpu affinity for more stable benchmark results Apr 11, 2023
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.

2 participants