Why child processes are needed in Node.js - Performance Evidence

Performance: Why child processes are needed

HIGH IMPACT

This concept affects how Node.js handles CPU-intensive tasks and parallel work, impacting responsiveness and throughput.

Running CPU-heavy tasks without blocking the main Node.js event loop

Node.js

import { fork } from 'child_process'; const child = fork('heavyTask.js'); child.on('message', msg => console.log(msg));

Runs heavy task in a separate process, keeping main event loop free and responsive.

📈 Performance GainMain process remains responsive; input delay minimized; CPU work parallelized.

Running CPU-heavy tasks without blocking the main Node.js event loop

Node.js

const heavyTask = () => { while(true) {} }; heavyTask();

Blocks the single-threaded event loop, freezing all other operations and delaying responses.

📉 Performance CostBlocks event loop indefinitely, causing infinite input delay (INP).

Performance Comparison

Pattern	CPU Blocking	Event Loop Delay	Memory Overhead	Verdict
Synchronous heavy task in main process	Blocks CPU fully	Blocks event loop causing high INP	Low memory but poor responsiveness	[X] Bad
Heavy task in child process	Runs in parallel CPU	Event loop remains free, low INP	Higher memory due to extra process	[OK] Good

Rendering Pipeline

Node.js main event loop delegates CPU-intensive work to child processes, preventing blocking and allowing asynchronous I/O to continue smoothly.

→Event Loop

→CPU Scheduling

→Inter-process Communication

⚠️ BottleneckEvent Loop blocking due to synchronous CPU-heavy tasks

Core Web Vital Affected

INP

This concept affects how Node.js handles CPU-intensive tasks and parallel work, impacting responsiveness and throughput.

Optimization Tips

1Never run CPU-heavy tasks synchronously in the main Node.js process.

2Use child processes to run heavy tasks in parallel and keep the event loop free.

3Expect higher memory use when using child processes but gain better responsiveness.

Performance Quiz - 3 Questions

Why should CPU-heavy tasks be moved to child processes in Node.js?

A To make the code run synchronously

B To prevent blocking the main event loop and keep the app responsive

C To reduce memory usage by sharing the same process

D To avoid using asynchronous callbacks

DevTools: Performance

How to check: Record a CPU profile while running your Node.js app; look for long blocking tasks in the main thread.

What to look for: Long synchronous tasks blocking the event loop indicate need for child processes; short tasks and responsive event loop indicate good use.

Practice

1. Why do Node.js applications use child processes?

easy

A. To make the app load faster on the internet

B. To reduce the size of the app files

C. To run heavy tasks without freezing the main app

D. To automatically update Node.js version

Solution

1. Step 1: Understand Node.js single-threaded nature

   Node.js runs JavaScript in a single thread, so heavy tasks can block the app.

2. Step 2: Role of child processes

   Child processes run tasks separately, so the main app stays responsive.

3. Final Answer:

   To run heavy tasks without freezing the main app -> Option C

4. Quick Check:

   Child processes prevent freezing = B [OK]

Hint: Child processes keep main app responsive during heavy work [OK]

Common Mistakes:

• Thinking child processes speed up internet loading
• Confusing file size with process management
• Believing child processes update Node.js automatically

2. Which of the following is the correct way to create a child process in Node.js?

easy

A. const child = require('child_process').fork('script.js');

B. const child = require('child_process').start('script.js');

C. const child = require('child_process').run('script.js');

D. const child = require('child_process').execute('script.js');

Solution

1. Step 1: Recall Node.js child process methods

   The 'child_process' module has methods like fork(), spawn(), exec(), but not start() or run().

2. Step 2: Identify correct method for creating a child process running a script

   fork() is used to create a new Node.js process running a script file.

3. Final Answer:

   const child = require('child_process').fork('script.js'); -> Option A

4. Quick Check:

   fork() creates child process = A [OK]

Hint: Use fork() to create child Node.js processes [OK]

Common Mistakes:

• Using non-existent methods like start() or run()
• Confusing exec() with fork() for script processes
• Forgetting to require 'child_process' module

3. What will be the output of this Node.js code snippet?

const { fork } = require('child_process');
const child = fork('child.js');
child.on('message', (msg) => {
  console.log('Message from child:', msg);
});
child.send('Hello');

Assuming child.js sends back the message { reply: 'Hi' } when it receives a message.

medium

A. No output because child.js is not executed

B. Message from child: Hello

C. Error: child.send is not a function

D. Message from child: { reply: 'Hi' }

Solution

1. Step 1: Understand message passing between parent and child

   The parent sends 'Hello' to child.js, which replies with { reply: 'Hi' }.

2. Step 2: Check event listener for 'message'

   The parent listens for messages from child and logs them with prefix 'Message from child:'.

3. Final Answer:

   Message from child: { reply: 'Hi' } -> Option D

4. Quick Check:

   Child replies logged correctly = D [OK]

Hint: Child sends message, parent logs with 'Message from child:' prefix [OK]

Common Mistakes:

• Confusing sent and received messages
• Expecting error from child.send() which is valid
• Assuming child.js does not run without error

4. Identify the error in this Node.js code using child processes:

const { fork } = require('child_process');
const child = fork('worker.js');
child.send('start');
child.on('message', (msg) => {
  console.log(msg);
});
child.on('error', (err) => {
  console.error('Child error:', err);
});

medium

A. Calling child.send() before setting up 'message' event listener

B. No error; code is correct

C. Not handling 'exit' event of child process

D. Missing require statement for 'child_process' module

Solution

1. Step 1: Check order of send() and event listeners

   It's valid to call send() before setting up 'message' listener; messages will queue.

2. Step 2: Verify required event handlers and module import

   Module is required correctly; 'error' event is handled; 'exit' event is optional.

3. Final Answer:

   No error; code is correct -> Option B

4. Quick Check:

   Code follows child process patterns = C [OK]

Hint: send() can be called anytime; event listeners catch messages/errors [OK]

Common Mistakes:

• Thinking send() must come after 'message' listener
• Expecting mandatory 'exit' event handling
• Missing module import (not in this code)

5. You want to perform a CPU-heavy task in Node.js without blocking the main event loop. Which approach best uses child processes to achieve this?

hard

A. Use fork() to run the heavy task in a separate process and communicate results via messages

B. Run the heavy task directly in the main thread and use setTimeout to delay it

C. Use exec() to run a shell command that blocks the main thread

D. Use require() to load the heavy task module synchronously

Solution

1. Step 1: Identify how to avoid blocking main event loop

   Heavy CPU tasks block the single-threaded main loop, causing freezes.

2. Step 2: Use child processes to run heavy tasks separately

   fork() creates a separate Node.js process to run the task without blocking.

3. Step 3: Communicate results safely

   Use message passing between main and child process to get results asynchronously.

4. Final Answer:

   Use fork() to run the heavy task in a separate process and communicate results via messages -> Option A

5. Quick Check:

   fork() isolates heavy tasks = A [OK]

Hint: fork() runs heavy tasks separately, keeping main loop free [OK]

Common Mistakes:

• Using setTimeout to delay heavy tasks (does not prevent blocking)
• Using exec() which can block main thread
• Loading heavy tasks synchronously with require()