---
title: "Discussion on \"The 7 Threads Running Inside Every Node.js Process\" | Hashnode"
description: "Discussion on \"The 7 Threads Running Inside Every Node.js Process\". Explore why an empty Node.js process launches 7 OS threads, what V8 does in the background, and how these threads differ from the libuv thread pool."
url: "https://hashnode.com/posts/why-an-empty-nodejs-process-runs-7-threads/6af6d73a41060513e7d11ea0"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The 7 Threads Running Inside Every Node.js Process](https://doogal.dev/why-an-empty-nodejs-process-runs-7-threads?utm_source=hashnode&utm_medium=feed)

Explore why an empty Node.js process launches 7 OS threads, what V8 does in the background, and how these threads differ from the libuv thread pool.

3h ago · 5 min read · doogal.dev  
Read the article

-   [#nodejs](https://hashnode.com/tag/nodejs)
-   [#javascript](https://hashnode.com/tag/javascript)
-   [#webdevelopment](https://hashnode.com/tag/webdevelopment)
-   [#softwareengineering](https://hashnode.com/tag/softwareengineering)

## Written by

[Doogal Simpson](https://hashnode.com/@doogal)

@doogal

  
[View profile](https://hashnode.com/@doogal)

"hey doogal, what is .... ?"

## Responses 1

Markdown supported · ⌘↵ to post

[OneLifeVibe](https://hashnode.com/@onelifevibe)

[1h ago](https://hashnode.com/posts/why-an-empty-nodejs-process-runs-7-threads/6af6d73a41060513e7d11ea0/comment/6af6f438998f15eb60c8fb73)

This clears up a confusion I have heard a lot. Saying Node is single threaded is true for the JavaScript, but it hides the work happening around it. Your table makes the split easy to follow, especially the four V8 threads for garbage collection and JIT work versus the separate libuv pool. The line I will remember is simple: JavaScript execution is single threaded, but the process executing it is multi threaded. That distinction makes debugging slow startups and blocked loops much easier to reason about.
