Skip to content

benchmark: use process.execPath when pinning CPUs in run.js - #66724

Open
RafaelGSS wants to merge 1 commit into
nodejs:mainfrom
RafaelGSS:use-process-execpath-when-pinning-cpus-in-run-js
Open

RafaelGSS wants to merge 1 commit into
nodejs:mainfrom
RafaelGSS:use-process-execpath-when-pinning-cpus-in-run-js

Conversation

@RafaelGSS

Copy link
Copy Markdown
Member

benchmark: use process.execPath when pinning CPUs in run.js

The taskset path used the node from PATH, not the running binary.

The taskset path used the node from PATH, not the running binary.

Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com>
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/performance

@nodejs-github-bot nodejs-github-bot added benchmark Issues and PRs related to Node.js benchmarks and benchmarking infrastructure. performance Issues and PRs related to the performance of Node.js. labels Oct 14, 2026
@RafaelGSS RafaelGSS added the author ready PRs with CI started, the required approvals, and no outstanding review comments. label Oct 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author ready PRs with CI started, the required approvals, and no outstanding review comments. benchmark Issues and PRs related to Node.js benchmarks and benchmarking infrastructure. performance Issues and PRs related to the performance of Node.js.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants