On Tue, Sep 18, 2012 at 1:27 PM, Michael <[email protected]> wrote: > hi, > > I am playing a bit with JMeter to produce some load on my Node.js system > (HTTP requests). I recognized, that under heavy load my master node process > in the cluster is using 100% CPU and will never stop doing so even if no > requests are arriving.I attached a screenshot... This was the situation some > minutes after the load. The whole system was relaxed again expect the master > in the cluster. > > My cluster is build like the example here > http://nodejs.org/api/cluster.html#cluster_cluster So there is nothing than > master.fork() in master's code. > > Any ideas what makes the master process busy? The application still respond > very fast in the 100% CPU master situation. > > Regards, > > Michael
Trace the program with strace on Linux or truss / dtruss if you're on a BSD or Solaris system, that should give you a hint what the process is doing. In case of doubt, post the trace output. Another option is to turn on profiling with --prof and inspect the call graph. `npm install profiler` will give you a nprof tool that parses the v8.log into human-readable form. -- 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
