Link Details

Link 1151923 thumbnail
User 1120917 avatar

By stronglooper
Published: May 09 2014 / 13:08

In last week’s performance tip, we discussed in detail how to diagnose memory leak problems with Node.js applications. In this go around we look at CPU profiling and how a good diagnosis can lead us to find the performance hotspots.
  • 9
  • 0
  • 507
  • 1913
User 1050383 avatar

ijroth replied ago:

0 votes Vote down Vote up Reply

When things go all async it can be difficult to figure out what is taking so long...

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Apache Hadoop
Written by: Piotr Krewski
Featured Refcardz: Top Refcardz:
  1. Play
  2. Akka
  3. Design Patterns
  4. OO JS
  5. Cont. Delivery
  1. Play
  2. Java Performance
  3. Akka
  4. REST
  5. Java