If it spikes to 100%, and then goes back down, I'd agree that sounds like garbage collection.
Either way, the best way to know what is going on is to profile it! I think on current versions of node, node-webkit-agent[1] is currently the best (only?) way to get a JavaScript CPU profile. If it reports all of the time in "(program)", then you may need a lower-level CPU profile to know what's going on. [1] https://github.com/c4milo/node-webkit-agent Jimb Esser On Wednesday, November 14, 2012 1:08:04 AM UTC-8, Dor Tzur wrote: > > We're having a problem where every once in a while one of our environments > our node app runs on 100% CPU. The server isn't very active and usually > runs on 0%-2% CPU. > I was wondering what are the common issues that might cause this problem > and what would be the best way to find out what causing this issue. > > technical spec: > node version 0.8.14 > ubuntu 11.10 > Intel(R) Xeon(R) CPU E5645 @ 2.40GHz > > gems used: > "express" : 2.5.x, "log" : "1.2.x", "redis" : "0.8.x", "socket.io" : > "0.9.x", "mongodb": ">= 0.9.6-7", "passport" : "0.x.x", "passport-local" : > "0.x.x", > > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: 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 post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
