Great tool which allows Node.js developers to take heap snapshot and inspect them later with Chrome Developer Tools. This module is useful because it can emit leak events if it sees the heap grow over 5 consecutive garbage collections. However you can easily find newer versions of it in GitHub’s fork list for the repository.
The original package was abandoned a long time ago and is no longer maintained. If you search for “how to find leak in node” the first tool you’d probably find is memwatch. Node.js Memory Leak Debugging Arsenal Memwatch Therefore my dream of having two application instances per 1X Heroku Dyno vanished. During peak load a new application instance could consume up to 270MB of RAM. Sounds like a very lightweight stack, right? Not quite. Overhead becomes very pricey when you need to serve many requests.įor the new API we chose restify with native MongoDB driver and Kue for background jobs. The original application occupied almost 600MB of RAM and therefore we decided to take the hot API endpoints and reimplement them. The application, an API server, was intended to be able to process hundreds of thousands of requests every minute. Recently I was asked to work on a Node.js application for one of my Toptal clients to fix a memory leak issue.
0 kommentar(er)
