[Solved] What is wrong with this worker pool implementation? const { Worker } = require('worker_threads'); function runTask() { const worker = new Worker('./worker.js'); worker.on('message', result => console.... | Node.js

Node.js - Worker Threads

What is wrong with this worker pool implementation?

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

function runTask() {
  const worker = new Worker('./worker.js');
  worker.on('message', result => console.log(result));
}

for (let i = 0; i < 10; i++) {
  runTask();
}

AIt uses a synchronous loop blocking the event loop

BIt creates a new worker for each task, which is inefficient

CIt does not listen for 'error' events on workers

DIt should use child_process instead of worker_threads

Step-by-Step Solution

Solution:

Step 1: Analyze worker creation in loop
The code creates a new worker for each task, which can be costly in resources.
Step 2: Identify inefficiency
Worker pool pattern reuses a fixed number of workers instead of creating many.
Final Answer:
It creates a new worker for each task, which is inefficient -> Option B
Quick Check:
Worker creation per task = Inefficient resource use [OK]

Quick Trick: Reuse workers instead of creating many for efficiency [OK]

Common Mistakes:

Ignoring error event listeners
Thinking synchronous loop blocks event loop here
Confusing worker_threads with child_process

Master "Worker Threads" in Node.js

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Perf

More Node.js Quizzes

What is wrong with this worker pool implementation?

Step 1: Analyze worker creation in loop

Step 2: Identify inefficiency

Final Answer:

Quick Check:

Want More Practice?