-
Notifications
You must be signed in to change notification settings - Fork 7
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
chore: add CPU pinning #157
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
@@ -101,7 +101,7 @@ fi | |||
fileName=output`date +%d%m%y-%H%M%S`.csv | |||
echo "Output will be saved to $fileName" | |||
pwd | |||
./node-master benchmark/compare.js --old ./node-master --new ./node-pr $FILTER $RUNS -- $CATEGORY | tee $fileName | |||
./node-master benchmark/compare.js --set CPUSET=0 --old ./node-master --new ./node-pr $FILTER $RUNS -- $CATEGORY | tee $fileName |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure CPUSET=0
is the desired setting -- wouldn't this set the benchmarks to only run on CPU 0?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nodejs/node#52233 (comment) suggests
So it should just be a matter of
taskset -c 0-11 <command>
for the perf cores.
So maybe CPUSET=0-11
? Or perhaps a better approach would be to parameterize (similar to e.g. $FILTER
, $RUNS
, etc.) and then we can set the parameter in Jenkins.
* Run on CPUs 0-11 (perf cores) Ref: #157 (comment) * add option to run on specific cpu set
Ref: nodejs/build#3657 (comment)