Creating worker threads in Node.js - Performance Optimization Steps

Performance: Creating worker threads

HIGH IMPACT

This concept affects how CPU-intensive tasks impact the main thread and overall responsiveness of a Node.js application.

Running CPU-heavy tasks without blocking the main thread

Node.js

import { Worker } from 'node:worker_threads';
const worker = new Worker(`
  const { parentPort } = require('worker_threads');
  for (let i = 0; i < 1e9; i++) {}
  parentPort.postMessage('done');
`, { eval: true });
worker.on('message', msg => console.log(msg));

Runs CPU-heavy task in a separate thread, keeping main thread free for other tasks and input handling.

📈 Performance GainMain thread remains responsive; input latency is low; heavy task runs in parallel.

Running CPU-heavy tasks without blocking the main thread

Node.js

const heavyTask = () => {
  // CPU-intensive loop
  for (let i = 0; i < 1e9; i++) {}
};
heavyTask();

This runs the heavy task on the main thread, blocking event loop and delaying all other operations.

📉 Performance CostBlocks main thread for hundreds of milliseconds, causing poor input responsiveness (high INP).

Performance Comparison

Pattern	CPU Usage	Main Thread Blocking	Responsiveness	Verdict
Synchronous heavy task on main thread	High CPU on main thread	Blocks main thread fully	Poor input responsiveness	[X] Bad
Heavy task in worker thread	High CPU but off main thread	Main thread free	Good input responsiveness	[OK] Good

Rendering Pipeline

In Node.js, the main thread handles event loop and I/O. Heavy synchronous tasks block this thread, delaying event processing. Worker threads run tasks in parallel, avoiding blocking the main thread.

→Event Loop

→Task Execution

⚠️ BottleneckMain thread blocking due to synchronous CPU work

Core Web Vital Affected

INP

This concept affects how CPU-intensive tasks impact the main thread and overall responsiveness of a Node.js application.

Optimization Tips

1Offload CPU-intensive tasks to worker threads to avoid blocking the main thread.

2Avoid synchronous heavy computations on the main thread to keep event loop responsive.

3Use worker threads to improve input responsiveness and reduce input latency (INP).

Performance Quiz - 3 Questions

What is the main performance benefit of using worker threads in Node.js?

A They reduce the total CPU usage of the application.

B They prevent blocking the main thread by running CPU-heavy tasks in parallel.

C They automatically optimize memory usage.

D They speed up network requests.

DevTools: Performance

How to check: Record a CPU profile while running your Node.js app with and without worker threads. Look for long main thread tasks blocking event loop.

What to look for: Long blocking tasks on main thread indicate poor performance; worker threads show parallel CPU usage without blocking main thread.

Practice

1. What is the main purpose of using worker_threads in Node.js?

easy

A. To handle HTTP requests faster

B. To simplify asynchronous callbacks

C. To manage database connections

D. To run code in parallel without blocking the main thread

Solution

1. Step 1: Understand worker threads role

   Worker threads allow running JavaScript code in parallel threads separate from the main thread.

2. Step 2: Compare with other options

   Options B, C, and D describe unrelated tasks; worker threads specifically help avoid blocking the main thread.

3. Final Answer:

   To run code in parallel without blocking the main thread -> Option D

4. Quick Check:

   Parallel code execution = A [OK]

Hint: Worker threads run code parallel to main thread [OK]

Common Mistakes:

• Confusing worker threads with async callbacks
• Thinking worker threads manage HTTP or DB tasks directly

2. Which of the following is the correct way to import the Worker class from the worker_threads module?

easy

A. const Worker = require('worker_threads');

B. import Worker from 'worker_threads';

C. const { Worker } = require('worker_threads');

D. const Worker = require('worker_threads').worker;

Solution

1. Step 1: Recall correct import syntax

   The Worker class is a named export, so we use destructuring: const { Worker } = require('worker_threads');

2. Step 2: Check other options

   const Worker = require('worker_threads'); assigns the entire module object, not the Worker class. import Worker from 'worker_threads'; uses ES module syntax which requires extra config. const Worker = require('worker_threads').worker; uses wrong property name.

3. Final Answer:

   const { Worker } = require('worker_threads'); -> Option C

4. Quick Check:

   Destructure Worker from module = D [OK]

Hint: Use destructuring to import Worker from worker_threads [OK]

Common Mistakes:

• Using wrong property name like 'worker' instead of 'Worker'
• Mixing CommonJS and ES module syntax incorrectly

3. What will be the output of the following code snippet?

const { Worker, isMainThread, parentPort } = require('worker_threads');

if (isMainThread) {
  const worker = new Worker(__filename);
  worker.on('message', msg => console.log('From worker:', msg));
  worker.postMessage('Hello');
} else {
  parentPort.on('message', msg => {
    parentPort.postMessage(msg + ' World');
  });
}

medium

A. From worker: Hello World

B. From worker: Hello

C. SyntaxError

D. No output

Solution

1. Step 1: Understand main and worker thread roles

   Main thread creates a worker running the same file. It sends 'Hello' to worker.

2. Step 2: Trace message passing

   Worker receives 'Hello', appends ' World', and sends back 'Hello World'. Main thread logs this message.

3. Final Answer:

   From worker: Hello World -> Option A

4. Quick Check:

   Message sent + ' World' logged = B [OK]

Hint: Worker appends ' World' and sends back message [OK]

Common Mistakes:

• Expecting original message without modification
• Confusing main thread and worker thread roles
• Missing event listeners for messages

4. Identify the error in this worker thread code snippet:

const { Worker } = require('worker_threads');

const worker = new Worker('worker.js');
worker.on('message', msg => console.log(msg));
worker.postMessage('Start');

medium

A. Worker file path should be absolute or URL

B. Missing event listener for 'error' event

C. Cannot create Worker with a string filename

D. Cannot call postMessage on Worker instance

Solution

1. Step 1: Check Worker constructor argument

   The Worker constructor expects an absolute path or a URL, not just a relative string like 'worker.js'.

2. Step 2: Validate other options

   Cannot create Worker with a string filename is incorrect because Worker can be created with a filename if path is correct. Missing event listener for 'error' event is good practice but not an error. Cannot call postMessage on Worker instance is wrong; postMessage is valid on Worker.

3. Final Answer:

   Worker file path should be absolute or URL -> Option A

4. Quick Check:

   Worker needs absolute path or URL = C [OK]

Hint: Use absolute path or URL for Worker file [OK]

Common Mistakes:

• Using relative paths without resolving them
• Ignoring error event listeners
• Thinking postMessage is invalid on Worker

5. You want to create a worker thread that performs a CPU-heavy calculation and sends the result back. Which approach correctly creates the worker and handles the result asynchronously?

hard

A. Use new Worker() without arguments and call worker.send() to communicate

B. Use new Worker('./calc.js') with worker.on('message', callback) and send data via worker.postMessage()

C. Use require('worker_threads').run() to start the worker and get a promise

D. Create a child process with child_process.fork() and communicate with worker.postMessage()

Solution

1. Step 1: Identify correct Worker creation and communication

   Creating a worker with new Worker('./calc.js') and using worker.on('message') plus worker.postMessage() is the standard pattern.

2. Step 2: Eliminate incorrect options

   Use new Worker() without arguments and call worker.send() to communicate is invalid because Worker requires a filename or code. Use require('worker_threads').run() to start the worker and get a promise is incorrect; no run() method exists. Create a child process with child_process.fork() and communicate with worker.postMessage() uses child_process, not worker_threads, and postMessage is not valid on child processes.

3. Final Answer:

   Use new Worker('./calc.js') with worker.on('message', callback) and send data via worker.postMessage() -> Option B

4. Quick Check:

   Worker with filename + message events = A [OK]

Hint: Use new Worker(filename) and message events for communication [OK]

Common Mistakes:

• Trying to create Worker without filename
• Confusing child_process with worker_threads
• Using non-existent Worker methods