#Nodejs memory monitor series#

Here is an example from in Node v0.12. The following example will show an easy way to add a memory leak in your code, even for trained eyes is hard to spot the problem: const connector = require('./lib/connector') Ĭonnector.on('connected', async (db) => = require('events') ĬtMaxListeners(0) // You will be able to attach Indefinitly events 1,941 2 12 6 Add a comment 5 Answers Sorted by: 222 The built-in process module has a method memoryUsage that offers insight in the memory usage of the current Node.js process. Also, we will do some analysis using node clinic tool and chrome dev-tools to identify a nasty memory leak. A rational way (in the short term) to postpone the problem is to restart the application before it. This post is about the top five Node.js performance metrics you should regularly monitor, namely: User-facing latencies.

If your backlog cant accomodate some time to investigate the leak in the near future, I advise to look for a temporary solution, and deal with the root cause later. However, if you want behind-the-scenes knowledge, read on. In the second part, we will focus on event emitters and cached objects. Finding and fixing a memory leak in Node.js takes time - usually a day or more. So, I wish to know when the application is running out of memory so I can immediately kill the Video Transcoder. For me, Im doing some video transcoding on the server and sometimes it leads to out of memory errors.

#Nodejs memory monitor series#

This article would be the second part of the series 'Understanding memory leaks in node' if you did not read the first part you can find it here. How can I know when my application is running out of memory.