Received: by 10.52.90.109 with SMTP id bv13mr2193584vdb.1.1347969231683; Tue, 18 Sep 2012 04:53:51 -0700 (PDT) X-BeenThere: nodejs@googlegroups.com Received: by 10.52.92.207 with SMTP id co15ls1848216vdb.5.gmail; Tue, 18 Sep 2012 04:53:43 -0700 (PDT) Received: by 10.58.91.100 with SMTP id cd4mr2812353veb.8.1347969223462; Tue, 18 Sep 2012 04:53:43 -0700 (PDT) Received: by 10.58.91.100 with SMTP id cd4mr2812351veb.8.1347969223448; Tue, 18 Sep 2012 04:53:43 -0700 (PDT) Return-Path: Received: from mail-vb0-f50.google.com (mail-vb0-f50.google.com [209.85.212.50]) by gmr-mx.google.com with ESMTPS id r14si529829vdu.1.2012.09.18.04.53.43 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 18 Sep 2012 04:53:43 -0700 (PDT) Received-SPF: pass (google.com: domain of fedor.indu...@gmail.com designates 209.85.212.50 as permitted sender) client-ip=209.85.212.50; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of fedor.indu...@gmail.com designates 209.85.212.50 as permitted sender) smtp.mail=fedor.indu...@gmail.com; dkim=pass header...@gmail.com Received: by vbnl22 with SMTP id l22so10320698vbn.37 for ; Tue, 18 Sep 2012 04:53:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=Kgb0D24OCb7/a8RIedIqmZ4sONMeBzrwQbJthmAW6tw=; b=i/DaIwyEpNeTvmSCnA9dZ43SH0nSi7iWOJGia4TAJ2mOeA7FFdgBfLjo3UFeJ1exwM p7o7Qr9dc8roHWFTatwX/bCdP1GvRkYoIkZOJrktVPIrdGRlrnKJAXVFhgBWsGc7Qr1L amJFvj7erohKDd2a+yUZcgAoOFoFmQoymSOfGUzieq1cUqOdA3JocbHuv+EzmSlbChQe RFmZ8NlGYhFCOkxi8eYn8nt1zy+pMI6hG++C9I3RR6lzkm2bZ+l7xWCl7pAy6jpFf89i fDhI6VDlp8DrNoB3Be8I39Wil6Cl2sRRebmDU0RPQGfbq4o25BvRfYiIXhDgyPEzMo0H 4dHw== Received: by 10.52.24.139 with SMTP id u11mr4902338vdf.15.1347969223096; Tue, 18 Sep 2012 04:53:43 -0700 (PDT) MIME-Version: 1.0 Sender: fedor.indu...@gmail.com Received: by 10.220.154.7 with HTTP; Tue, 18 Sep 2012 04:53:22 -0700 (PDT) In-Reply-To: References: From: Fedor Indutny Date: Tue, 18 Sep 2012 15:53:22 +0400 Message-ID: Subject: Re: [nodejs] Noe.js cluster master at 100% CPU To: nodejs@googlegroups.com Content-Type: multipart/alternative; boundary=bcaec501c572b5fa5104c9f88ad5 --bcaec501c572b5fa5104c9f88ad5 Content-Type: text/plain; charset=ISO-8859-1 And btw, what node.js version are you using? On Tue, Sep 18, 2012 at 3:37 PM, Ben Noordhuis wrote: > On Tue, Sep 18, 2012 at 1:27 PM, Michael 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 nodejs@googlegroups.com > To unsubscribe from this group, send email to > nodejs+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > --bcaec501c572b5fa5104c9f88ad5 Content-Type: text/html; charset=ISO-8859-1 And btw, what node.js version are you using?


On Tue, Sep 18, 2012 at 3:37 PM, Ben Noordhuis <i...@bnoordhuis.nl> wrote:
On Tue, Sep 18, 2012 at 1:27 PM, Michael <michael.wit...@cinovo.de> 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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--bcaec501c572b5fa5104c9f88ad5--