Questions And Answers

More Tutorials

NodeJS Getting started with Nodes profiling

Profiling a simple node application

Step 1 : Install the node-inspector package using npm globally on you machine

$ npm install -g node-inspector

Step 2 : Start the node-inspector server

$ node-inspector

Step 3 : Start debugging your node application

$ node --debug-brk your/short/node/script.js

Step 4 :Open in the Chrome browser. And you will see a chrom-dev tools interface with your nodejs application source code in left panel . And since we have used debug break option while debugging the application the code execution will stop at the first line of code.

Step 5 : This is the easy part where you switch to the profiling tab and start profiling the application . In case you want get the profile for a particular method or flow make sure the code execution is break-pointed just before that piece of code is executed.

Step 6 : Once you have recorded your CPU profile or heap dump/snapshot or heap allocation you can then view the results in the same window or save them to local drive for later analysis or comparison with other profiles.


In this page (written and validated by ) you learned about NodeJS Getting started with Nodes profiling . What's Next? If you are interested in completing NodeJS tutorial, your next topic will be learning about: NodeJS Performance.

Incorrect info or code snippet? We take very seriously the accuracy of the information provided on our website. We also make sure to test all snippets and examples provided for each section. If you find any incorrect information, please send us an email about the issue:

Share On:

Mockstacks was launched to help beginners learn programming languages; the site is optimized with no Ads as, Ads might slow down the performance. We also don't track any personal information; we also don't collect any kind of data unless the user provided us a corrected information. Almost all examples have been tested. Tutorials, references, and examples are constantly reviewed to avoid errors, but we cannot warrant full correctness of all content. By using, you agree to have read and accepted our terms of use, cookies and privacy policy.