context1: set cpu affinity for more stable benchmark results #80
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
"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]>
|
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
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
"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]