What are the application scenarios of subprocesses in Node.js?-JS Tutorial-php.cn

What are the application scenarios of subprocesses in Node.js?

亚连

Release： 2018-06-09 16:26:31

Original

1444 people have browsed it

This article mainly introduces a brief discussion of Node.js sub-processes and application scenarios. Now I share it with you and give it as a reference.

Background

Since ons (Alibaba Cloud RocketMQ package) is encapsulated based on C++, it does not support the instantiation of multiple producers and consumers in a single process. In order to To solve this problem, Node.js child process is used.

Pits encountered during use

Release: After process management closes the main process, the child process becomes an operating system process (pid is 1)

Several solutions

Treat the child process as an independent running process, record the pid, and process management to close the main process and close the child process at the same time when publishing

The main process monitors the shutdown event, Actively close the child process belonging to itself

Type of child process

spawn: Execute command
exec: execute command (new shell)
execFile: execute file
fork: execute file

Common events for child processes

exit
##close
error
message

There is a difference between close and exit. close is an event triggered when the data flow is closed, and exit is an event triggered when the data flow is closed. Event triggered when the process exits. Because multiple child processes can share the same data stream, the close event may not necessarily be triggered when a child process exits, because there are other child processes using the data stream at this time.

Subprocess data flow

stdin
stdout
stderr

#Because the main process is the starting point, the data flow of the sub-process is opposite to the conventionally understood data flow direction. stdin: write stream, stdout, stderr: Read stream.

spawn

spawn(command[, args][, options])

Copy after login

Execute a command and return various execution results through the data data stream.

Basic usage

const { spawn } = require(&#39;child_process&#39;);

const child = spawn(&#39;find&#39;, [ &#39;.&#39;, &#39;-type&#39;, &#39;f&#39; ]);
child.stdout.on(&#39;data&#39;, (data) => {
  console.log(`child stdout:\n${data}`);
});

child.stderr.on(&#39;data&#39;, (data) => {
  console.error(`child stderr:\n${data}`);
});

child.on(&#39;exit&#39;, (code, signal) => {
  console.log(`child process exit with: code $[code], signal: ${signal}`);
});

Copy after login

Common parameters

{
  cwd: String,
  env: Object,
  stdio: Array | String,
  detached: Boolean,
  shell: Boolean,
  uid: Number,
  gid: Number
}

Copy after login

Focus on the detached attribute. Setting detached to true is to prepare the child process to run independently. The specific behavior of the child process is related to the operating system. Different systems behave differently. The Windows system child process will have its own console window, and the POSIX system child process will become the new process group and session leader.

At this time, the child process is not completely independent. The running results of the child process will be displayed on the data stream set by the main process, and the exit of the main process will affect the operation of the child process. When stdio is set to ignore and child.unref(); is called, the child process begins to truly run independently, and the main process can exit independently.

exec

exec(command[, options][, callback])

Copy after login

Execute a command and return the result through the callback parameter. When the command is not executed, part of the result will be cached in the system memory.

const { exec } = require(&#39;child_process&#39;);

exec(&#39;find . -type f | wc -l&#39;, (err, stdout, stderr) => {
  if (err) {
    console.error(`exec error: ${err}`);
    return;
  }

  console.log(`Number of files ${stdout}`);
});

Copy after login

The best of both worlds - spawn instead of exec

Since the result of exec is returned once and is cached in memory before returning, the shell command being executed When the output is too large, using exec to execute the command cannot complete our work as expected. At this time, we can use spawn instead of exec to execute the shell command.

const { spawn } = require(&#39;child_process&#39;);

const child = spawn(&#39;find . -type f | wc -l&#39;, {
  stdio: &#39;inherit&#39;,
  shell: true
});

child.stdout.on(&#39;data&#39;, (data) => {
  console.log(`child stdout:\n${data}`);
});

child.stderr.on(&#39;data&#39;, (data) => {
  console.error(`child stderr:\n${data}`);
});

child.on(&#39;exit&#39;, (code, signal) => {
  console.log(`child process exit with: code $[code], signal: ${signal}`);
});

Copy after login

execFile

child_process.execFile(file[, args][, options][, callback])

Copy after login

Execute a file

The function is basically the same as exec, except that it executes a script file with a given path, and It is to directly create a new process instead of creating a shell environment and then running the script, which is relatively lightweight and more efficient. However, in Windows systems, files such as .cmd and .bat cannot be run directly. This means that execFile will not work. You can use spawn and exec instead.

fork

child_process.fork(modulePath[, args][, options])

Copy after login

Execute a Node.js file

// parent.js

const { fork } = require(&#39;child_process&#39;);

const child = fork(&#39;child.js&#39;);

child.on(&#39;message&#39;, (msg) => {
  console.log(&#39;Message from child&#39;, msg);
});

child.send({ hello: &#39;world&#39; });

Copy after login

// child.js

process.on(&#39;message&#39;, (msg) => {
  console.log(&#39;Message from parent:&#39;, msg);
});

let counter = 0;

setInterval(() => {
  process.send({ counter: counter++ });
}, 3000);

Copy after login

fork is actually a special form of spawn, which fixes the spawn Node.js process. And a communication channel is established between the master and child processes, so that the master and child processes can use the process module to communicate based on events.

Subprocess usage scenarios

Computationally intensive systems
Front-end build tools utilize multi-core CPUs Parallel computing, improve construction efficiency
Process management tools, such as: some functions in PM2

The above is what I compiled for everyone, I hope that in the future It will be helpful to everyone.

About the use of vue-fontawesome in vue.js

Use JS to add new elements to the node

About the actual usage of log4js in Express

How to reference the Ali font icon in vue

Through Node .js uses MySQL connection pool

The above is the detailed content of What are the application scenarios of subprocesses in Node.js?. For more information, please follow other related articles on the PHP Chinese website!