How cluster module works in Node.js - Performance Optimization Steps

Performance: How cluster module works

MEDIUM IMPACT

This affects how Node.js handles multiple CPU cores to improve server throughput and responsiveness.

Handling high concurrent requests in a Node.js server

Node.js

import cluster from 'node:cluster';
import http from 'http';
import os from 'node:os';

if (cluster.isPrimary) {
  const cpus = os.cpus().length;
  for (let i = 0; i < cpus; i++) {
    cluster.fork();
  }
} else {
  http.createServer((req, res) => {
    // heavy synchronous task
    for (let i = 0; i < 1e9; i++) {}
    res.end('Done');
  }).listen(3000);
}

Spreads load across CPU cores with multiple processes, preventing single event loop blocking.

📈 Performance GainImproves INP by parallelizing workload, reducing request delays.

Handling high concurrent requests in a Node.js server

Node.js

import http from 'http';

const server = http.createServer((req, res) => {
  // heavy synchronous task
  for (let i = 0; i < 1e9; i++) {}
  res.end('Done');
});

server.listen(3000);

Single process blocks event loop during heavy tasks, causing slow response and poor input responsiveness.

📉 Performance CostBlocks event loop, causing high INP and slow response under load.

Performance Comparison

Pattern	CPU Utilization	Event Loop Blocking	Request Throughput	Verdict
Single process server	Uses 1 core	High under load	Low	[X] Bad
Cluster with multiple workers	Uses all cores	Low per process	High	[OK] Good

Rendering Pipeline

The cluster module creates multiple Node.js processes that share server ports. Each process runs its own event loop, allowing parallel request handling.

→Event Loop

→CPU Utilization

→Request Handling

⚠️ BottleneckSingle-threaded event loop blocking in one process

Core Web Vital Affected

INP

This affects how Node.js handles multiple CPU cores to improve server throughput and responsiveness.

Optimization Tips

1Use cluster to utilize all CPU cores for better throughput.

2Avoid heavy synchronous code in a single process to prevent event loop blocking.

3Monitor CPU and event loop delays to measure cluster effectiveness.

Performance Quiz - 3 Questions

What is the main performance benefit of using the Node.js cluster module?

A It speeds up JavaScript execution within a single thread.

B It reduces the size of the Node.js bundle.

C It allows using multiple CPU cores to handle requests in parallel.

D It caches HTTP responses automatically.

DevTools: Performance

How to check: Run your Node.js server with and without cluster. Use CPU profiling in DevTools to see CPU usage and event loop delays.

What to look for: Look for CPU usage across cores and event loop blocking time. Cluster should show balanced CPU and less blocking.

Practice

1. What is the main purpose of the cluster module in Node.js?

easy

A. To provide a graphical user interface for Node.js apps

B. To manage database connections efficiently

C. To handle file system operations asynchronously

D. To create multiple worker processes to use all CPU cores

Solution

1. Step 1: Understand the cluster module role

   The cluster module allows Node.js to create multiple worker processes.

2. Step 2: Recognize the benefit

   These workers use all CPU cores to improve performance by handling requests in parallel.

3. Final Answer:

   To create multiple worker processes to use all CPU cores -> Option D

4. Quick Check:

   cluster module = multiple workers for CPU cores [OK]

Hint: Cluster = multiple processes for CPU cores [OK]

Common Mistakes:

• Confusing cluster with database or file system modules
• Thinking cluster manages UI or frontend
• Assuming cluster runs code in a single process

2. Which of the following is the correct way to check if the current process is the master in a cluster setup?

easy

A. if (cluster.isMaster) { ... }

B. if (cluster.isPrimary) { ... }

C. if (cluster.isWorker) { ... }

D. if (cluster.isMain) { ... }

Solution

1. Step 1: Recall the updated property name

   In recent Node.js versions, cluster.isPrimary replaces cluster.isMaster.

2. Step 2: Identify the correct syntax

   Using cluster.isPrimary correctly checks if the process is the primary (master) process.

3. Final Answer:

   if (cluster.isPrimary) { ... } -> Option B

4. Quick Check:

   Primary process check = cluster.isPrimary [OK]

Hint: Use cluster.isPrimary, not isMaster [OK]

Common Mistakes:

• Using deprecated cluster.isMaster instead of cluster.isPrimary
• Confusing isWorker with isPrimary
• Using non-existent properties like isMain

3. Consider this Node.js cluster code snippet:

const cluster = require('cluster');
const http = require('http');

if (cluster.isPrimary) {
  cluster.fork();
  cluster.fork();
} else {
  http.createServer((req, res) => {
    res.end('Worker ' + process.pid);
  }).listen(8000);
}

What will happen when you visit http://localhost:8000 multiple times?

medium

A. You will see responses from different worker process IDs

B. Only one worker will handle all requests

C. The server will crash because of multiple forks

D. You will get a syntax error on startup

Solution

1. Step 1: Understand cluster.fork creates workers

   Two workers are created, each running the HTTP server on port 8000.

2. Step 2: Recognize load balancing behavior

   Requests are distributed between workers, so responses show different process IDs.

3. Final Answer:

   You will see responses from different worker process IDs -> Option A

4. Quick Check:

   Multiple workers share port, respond with different PIDs [OK]

Hint: Multiple forks = multiple workers respond differently [OK]

Common Mistakes:

• Thinking only one worker handles all requests
• Assuming server crashes due to multiple forks
• Expecting syntax errors from this code

4. What is wrong with this cluster code snippet?

const cluster = require('cluster');
if (cluster.isPrimary) {
  cluster.fork();
} else {
  console.log('Worker running');
}

medium

A. cluster.isPrimary is deprecated, should use isMaster

B. No call to cluster.fork in the worker process

C. Missing server code inside worker

D. No error, code works fine

Solution

1. Step 1: Check cluster usage

   The primary forks one worker, which only logs a message but does not start a server.

2. Step 2: Identify missing functionality

   Without server code, the worker does not handle requests, so the cluster setup is incomplete.

3. Final Answer:

   Missing server code inside worker -> Option C

4. Quick Check:

   Worker must run server code to handle requests [OK]

Hint: Workers need server code to handle requests [OK]

Common Mistakes:

• Confusing isPrimary with deprecated isMaster
• Expecting cluster.fork in worker process
• Assuming code runs without server in worker

5. You want to create a cluster that automatically restarts a worker if it crashes. Which approach correctly implements this behavior?

hard

A. Listen to the 'exit' event on cluster and fork a new worker inside the handler

B. Use setInterval to fork new workers every second

C. Call cluster.fork() only once at startup and never again

D. Use cluster.disconnect() inside the worker to restart itself

Solution

1. Step 1: Understand worker crash handling

   The primary process can listen to the 'exit' event when a worker dies.

2. Step 2: Restart worker on exit

   Inside the 'exit' event handler, calling cluster.fork() creates a new worker to replace the crashed one.

3. Final Answer:

   Listen to the 'exit' event on cluster and fork a new worker inside the handler -> Option A

4. Quick Check:

   Restart crashed workers by handling 'exit' event [OK]

Hint: Use 'exit' event to restart workers automatically [OK]

Common Mistakes:

• Forking workers repeatedly with setInterval causes overload
• Not restarting workers after crash leads to downtime
• Using cluster.disconnect() inside worker does not restart it