Profiling the Unexpected in Node.js

February 12, 2015

Performance testing a Node.js application can be painful. Tooling can be a nightmare to set-up, and online help is almost non-existent. And even with the perfect setup in place… what are you even supposed to be looking for?

This is the position that we found ourselves in last year at Box, and this talk is the story of everything we’ve learned since. Instead of listing every relevant tool or teaching you how to setup awesome flame graphs, I share the surprising and unexpected things we learned about Node.js performance at Box, and how we reduced server response times by over 80% along the way.

Sometimes just knowing what to look for is half the battle.



The video for this talk has been posted to the NodeSummit conference website. Unfortunately it cannot be embedded here.