Thread Pool and Worker Threads Interview Questions for Node.js

Thread Pool and Worker Threads Interview Questions for Node.js

Thread pool and worker threads come up in deep Node.js interviews. Here are the common questions.

What is the libuv thread pool and what does it do?

A pool of 4 threads (by default) in libuv that handles operations the OS cannot do asynchronously: certain fs operations, dns.lookup, and some crypto. These run off the main thread, and callbacks run on the main thread via the event loop.

Which operations use the thread pool in Node.js?

File system operations (fs module), DNS lookups (dns.lookup), some crypto operations (crypto.pbkdf2, crypto.scrypt), and some zlib operations. Network I/O does not; it uses the OS's async capabilities directly.

What is the difference between the thread pool and worker threads?

The thread pool is internal to libuv and handles specific operations automatically. Worker threads are a Node.js API where your JavaScript code runs on separate threads for CPU-heavy computation. The thread pool is for I/O; worker threads are for computation.

How do you tune the thread pool size in Node.js?

Set UV_THREADPOOL_SIZE in the environment before starting Node.js. The default is 4. Increase it for apps with many fs, DNS, or crypto operations, but monitor CPU usage since more threads mean more contention.

When would you use worker threads in Node.js?

For heavy CPU computation like image processing, crypto on the JS side, or large data processing. Worker threads run your code on separate threads, keeping the main thread's event loop free for other requests.

The Takeaway

Know the thread pool (what it is, which operations use it, how to tune it), the difference from worker threads (internal vs your code, I/O vs computation), and when to use worker threads (CPU-heavy work). These test real depth in Node.js internals.