-
Notifications
You must be signed in to change notification settings - Fork 30k
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
benchmark: fix child-process-read on Windows #6971
Conversation
ec91385
to
7402cc2
Compare
@@ -1,7 +1,14 @@ | |||
'use strict'; | |||
var common = require('../common.js'); | |||
var os = require('os'); | |||
|
|||
var messagesLenght = [64, 256, 1024, 4096]; |
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.
Length is spelled wrong throughout this file.
Under Windows 'ipc' communication requires the other process to format its messages with 'IPC framing protocol'. Otherwise, an assert is triggered in libuv. This commit changes child-process-read benchmark to use stdout to communicate with parent process. It also adds child-process-read-ipc.js to benchmark IPC communication using child node process.
a96c1c6
to
4961a5d
Compare
I've corrected the spelling, PTAL |
LGTM cc @nodejs/benchmarking |
if (process.argv[2] === 'child') | ||
{ | ||
const len = +process.argv[3]; | ||
const msg = '"' + Array(len).join('.') + '"'; |
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.
const msg = `"${'.'.repeat(len)}"`;
LGTM with a nit |
Updated, PTAL |
Thanks @bzoz . Will land tomorrow if there are no further issues. |
Under Windows 'ipc' communication requires the other process to format its messages with 'IPC framing protocol'. Otherwise, an assert is triggered in libuv. This commit changes child-process-read benchmark to use stdout to communicate with parent process. It also adds child-process-read-ipc.js to benchmark IPC communication using child node process. PR-URL: #6971 Reviewed-By: João Reis <reis@janeasystems.com> Reviewed-By: James M Snell <jasnell@gmail.com>
CI: https://ci.nodejs.org/job/node-test-pull-request/2964/ (failures unrelated) Landed in cbbdc29 Thanks! |
Under Windows 'ipc' communication requires the other process to format its messages with 'IPC framing protocol'. Otherwise, an assert is triggered in libuv. This commit changes child-process-read benchmark to use stdout to communicate with parent process. It also adds child-process-read-ipc.js to benchmark IPC communication using child node process. PR-URL: #6971 Reviewed-By: João Reis <reis@janeasystems.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Checklist
Affected core subsystem(s)
benchmark
Description of change
Under Windows
ipc
communication requires the other process to format its messages with 'IPC framing protocol'. Otherwise, an assert is triggered in libuv. This commit changeschild-process-read.js
benchmark to use stdout to communicate with parent process. It also addschild-process-read-ipc.js
to benchmark IPC communication using child node process.