Long garbage collection(GC) pauses can contribute to many performance problems that arise in web application backends written in VM-based dynamic languages. Node.js, as a relatively new technology based on the V8 JavaScript engine, still doesn't have much tools to tackle this problem, and at the moment there aren't many documentation or articles about V8 GC logs either - to really understand those logs, you still have to dive into the V8 source code.
In this talk, I'll talk about our team's experiences in analyzing the V8 GC logs, hopefully saving you the trouble of digging around the V8 source code:
A brief introduction to V8 GC
How to obtain and read the V8 GC logs(based on v8 4.5.103.35, the one used by Node v4.x)
How to analyze the V8 GC logs and gain insight into the performance of your Node.js applications
About me: I'm an intern at alinode, currently working on analysis and visualization of V8 GC logs, heapdumps and CPU profiles.
Long garbage collection(GC) pauses can contribute to many performance problems that arise in web application backends written in VM-based dynamic languages. Node.js, as a relatively new technology based on the V8 JavaScript engine, still doesn't have much tools to tackle this problem, and at the moment there aren't many documentation or articles about V8 GC logs either - to really understand those logs, you still have to dive into the V8 source code.
In this talk, I'll talk about our team's experiences in analyzing the V8 GC logs, hopefully saving you the trouble of digging around the V8 source code:
About me: I'm an intern at alinode, currently working on analysis and visualization of V8 GC logs, heapdumps and CPU profiles.