Every Node.Js Engineer has faced some kind of issues with the GC, and had to debug it. The most common option is to use the —trace-gc, but did You know that there are multiple options to trace the GC? You can read the ones that I have used in the past and helped me fix problems.

Becoming a Top 1% Node.Js Engineer: GC Tracing Options

In previous posts, we’ve covered various aspects of the garbage collector in V8, from the minor GC scavenger algorithm to the possibility…

medium.com/p/2a20495f143c

Read the article

A list of articles to read if the current article triggered your curiosity.

Uncovering Node.js Internals: Minor Garbage Collection Algorithms

In Node.js, memory management is a critical aspect of performance. The V8 engine, which powers Node.js, uses two different types of garbage…

javascript.plainenglish.io/uncovering-node-js-internals-minor-garbage-collection-algorithms-c0ede581a57c

Uncovering Node.js Internals: Default Heap Sizing and Building Blocks

In our last blog post, we explored the structure of the heap in the V8 engine, delving into its various spaces. This time, we will unveil…

medium.com/@pkulcsarsz/uncovering-node-js-internals-default-heap-sizing-and-building-blocks-ae735a64ae17

List of interesting articles I read from the last publish

Feedback loop

If you could change one thing in the article or the newsletter what would it be? Feel free to reply to this email!

Keep reading

View more
caret-right
© 2026 Top 1% Node.Js Engineer.
beehiivPowered by beehiiv