Demystifying Memory Leaks and Profiling in Node.js

Today it is possible to write complex Node.js applications with only a handful of developers in a short time frame by relying upon Frameworks and tooling. But what happens when the application crashes with out of memory errors? How is it possible to guarantee fast response times? These problems are still considered difficult to solve.

Let's dive into the Node.js internals and learn about profilers and the garbage collector. Understanding how the system works in depth let's you write code that is safer, faster and less error prone.

Let's make sure you always provide the best experience for everyone. Yourself and your customer. Let us find that memory leak and fix it.


Participants would ideally know basics about the memory handling in JavaScript and know how to identify bottlenecks in applications.


* Participants understand the Node.js memory handling and their shortcomings.
* Participants know when to profile their application to identify memory leaks and slow code.
* Participants are able to find and address most memory leaks.




Ruben Bridgewater
Ruben Bridgewater Ruben is member of the Node.js Technical Steering Committee (TSC) and works as Senior IT-Architect for MaibornWolff GmbH. His main emphasis is building powerful and easy-to-use APIs for scalable and fast applications. He is continuously working with the V8 team and the TC39 committee to improve the developer experience with JavaScript.



Ihr möchtet über die enterJS
auf dem Laufenden gehalten werden?