In last week’s performance tip<http://strongloop.com/strongblog/node-js-performance-tip-of-the-week-memory-leak-diagnosis/>, 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.
http://strongloop.com/strongblog/node-js-performance-tip-cpu-profiler/ -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/42048556-6f8c-4ec4-8b41-b80bbd4bedf6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
