IPC communication between processes in Node.js - Performance & Optimization

Performance: IPC communication between processes

MEDIUM IMPACT

This affects the responsiveness and throughput of applications that rely on multiple Node.js processes communicating with each other.

Sending frequent large data chunks between Node.js processes

Node.js

const { fork } = require('child_process');
const child = fork('child.js');

setInterval(() => {
  const smallData = { timestamp: Date.now() };
  child.send(smallData);
}, 100);

Sending small, simple messages less frequently reduces CPU load and event loop blocking, improving responsiveness.

📈 Performance GainNon-blocking message passing; reduces CPU spikes; lowers INP

Sending frequent large data chunks between Node.js processes

Node.js

const { fork } = require('child_process');
const child = fork('child.js');

setInterval(() => {
  const largeData = Buffer.alloc(10 * 1024 * 1024, 'a'); // 10MB buffer
  child.send(largeData);
}, 10);

Sending large buffers very frequently causes high CPU usage and blocks the event loop, leading to slow message processing and increased latency.

📉 Performance CostBlocks event loop for tens of milliseconds per message; high CPU usage; increases INP (input delay)

Performance Comparison

Pattern	Message Size	Frequency	Event Loop Impact	Verdict
Large frequent messages	10MB	Every 10ms	Blocks event loop for 10-20ms	[X] Bad
Small infrequent messages	Few bytes	Every 100ms	Minimal event loop impact	[OK] Good

Rendering Pipeline

IPC messages pass through the Node.js event loop and underlying OS pipes or sockets. Large or frequent messages cause event loop delays and increase CPU usage, slowing message handling and responsiveness.

→Event Loop

→Message Queue

→CPU Processing

⚠️ BottleneckEvent Loop blocking due to large or frequent message serialization and deserialization

Core Web Vital Affected

INP

This affects the responsiveness and throughput of applications that rely on multiple Node.js processes communicating with each other.

Optimization Tips

1Avoid sending large data chunks frequently between processes.

2Use small, simple messages to keep the event loop responsive.

3Profile IPC communication to detect event loop blocking and optimize accordingly.

Performance Quiz - 3 Questions

What is the main performance issue when sending large messages very frequently between Node.js processes?

A Memory leaks in the child process

B Increased network latency

C Event loop blocking and high CPU usage

D Slow disk I/O

DevTools: Performance

How to check: Record a CPU profile while running IPC communication; look for long tasks or event loop blocking during message sends and receives.

What to look for: Long blocking tasks in the timeline and high CPU usage spikes indicate poor IPC performance.

Practice

1. What does IPC stand for in Node.js context and why is it useful?

easy

A. Internet Protocol Communication; it handles network requests.

B. Internal Process Control; it manages process memory usage.

C. Input-Process-Cache; it speeds up data processing.

D. Inter-Process Communication; it allows processes to exchange messages.

Solution

1. Step 1: Understand IPC meaning and its use in Node.js

   IPC means Inter-Process Communication, which is about processes exchanging data. In Node.js, IPC lets parent and child processes send messages to coordinate work.

2. Final Answer:

   Inter-Process Communication; it allows processes to exchange messages. -> Option D

3. Quick Check:

   IPC = Inter-Process Communication [OK]

Hint: IPC means processes talking to each other [OK]

Common Mistakes:

• Confusing IPC with network protocols
• Thinking IPC manages memory or caching
• Mixing up IPC with internal process controls

2. Which Node.js method is used to create a child process that supports IPC?

easy

A. child_process.spawn()

B. child_process.exec()

C. child_process.fork()

D. child_process.execFile()

Solution

1. Step 1: Review child process methods and identify the one enabling IPC

   spawn(), exec(), execFile() create processes but don't enable IPC by default. fork() creates a child process with an IPC channel for message passing.

2. Final Answer:

   child_process.fork() -> Option C

3. Quick Check:

   fork() creates IPC-enabled child process [OK]

Hint: Use fork() for IPC between parent and child [OK]

Common Mistakes:

• Using spawn() or exec() expecting IPC
• Confusing execFile() with fork()
• Not knowing fork() creates a special IPC channel

3. What will the following code output?

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

// child.js content:
process.on('message', msg => {
  process.send(msg + ' World');
});

medium

A. Parent got: World

B. Parent got: Hello World

C. No output, error occurs

D. Parent got: Hello

Solution

1. Step 1: Trace the message flow and parent's message handler

   The parent sends 'Hello' to child; child appends ' World' and sends back. Parent logs 'Parent got:' plus the message received from child.

2. Final Answer:

   Parent got: Hello World -> Option B

3. Quick Check:

   Child appends ' World' and parent logs it [OK]

Hint: Child appends ' World' before sending back [OK]

Common Mistakes:

• Expecting parent to log original 'Hello' only
• Thinking child does not send a message back
• Confusing message event direction

4. Identify the error in this IPC code snippet:

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

// child.js
process.send('Ready');
process.on('message', msg => console.log('Child got:', msg));

medium

A. Parent sends message before child process is ready to receive.

B. Child process sends message before 'message' event listener is set.

C. Child process calls process.send() before parent listens.

D. No error; code works correctly.

Solution

1. Step 1: Analyze message timing and understand child readiness

   Parent sends 'Start' immediately after fork; child may not be ready yet. Child sends 'Ready' immediately but parent may miss it if not listening yet.

2. Final Answer:

   Parent sends message before child process is ready to receive. -> Option A

3. Quick Check:

   Parent must wait for child's 'Ready' before sending [OK]

Hint: Wait for child's ready message before sending [OK]

Common Mistakes:

• Assuming child is ready immediately after fork
• Ignoring asynchronous nature of IPC
• Thinking process.send() order causes error

5. You want to create a Node.js parent process that forks two child processes. Each child sends a number to the parent, and the parent must send back the sum of both numbers to each child. Which approach correctly implements this IPC communication?

hard

A. Parent listens to both children messages, sums numbers, then sends sum to each child using child.send(sum).

B. Each child sends its number to the other child directly using process.send().

C. Parent forks children but does not set up message listeners; children communicate directly.

D. Children send numbers to parent, but parent sends sum only to the first child.

Solution

1. Step 1: Understand parent-child communication and message handling

   Children cannot send messages directly to each other; parent mediates IPC. Parent listens to messages from both children, calculates sum, then sends sum back to each child.

2. Final Answer:

   Parent listens to both children messages, sums numbers, then sends sum to each child using child.send(sum). -> Option A

3. Quick Check:

   Parent mediates and broadcasts sum to children [OK]

Hint: Parent must mediate messages and send sum to all children [OK]

Common Mistakes:

• Trying to send messages directly between children
• Not sending sum to both children
• Not listening to both children's messages in parent