FAQ
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

--
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

Search Discussions

  • Ben Noordhuis at Sep 18, 2012 at 11:37 am

    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
  • Fedor Indutny at Sep 18, 2012 at 11:53 am
    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
    --
    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
  • Michael at Sep 19, 2012 at 3:07 pm
    0.8.9 on linux build from source.

    Am Dienstag, 18. September 2012 13:53:51 UTC+2 schrieb Fedor Indutny:
    And btw, what node.js version are you using?


    On Tue, Sep 18, 2012 at 3:37 PM, Ben Noordhuis <in...@bnoordhuis.nl<javascript:>
    wrote:
    On Tue, Sep 18, 2012 at 1:27 PM, Michael <michael...@cinovo.de<javascript:>>
    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 nod...@googlegroups.com<javascript:>
    To unsubscribe from this group, send email to
    nodejs+un...@googlegroups.com <javascript:>
    For more options, visit this group at
    http://groups.google.com/group/nodejs?hl=en?hl=en
    --
    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
  • Fedor Indutny at Sep 28, 2012 at 3:22 pm
    And what about trace?

    Cheers,
    Fedor.


    On Wed, Sep 19, 2012 at 7:01 PM, Michael wrote:

    0.8.9 on linux build from source.

    Am Dienstag, 18. September 2012 13:53:51 UTC+2 schrieb Fedor Indutny:
    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<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<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 nod...@googlegroups.com

    To unsubscribe from this group, send email to
    nodejs+un...@**googlegroups.com

    For more options, visit this group at
    http://groups.google.com/**group/nodejs?hl=en?hl=en<http://groups.google.com/group/nodejs?hl=en?hl=en>
    --
    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

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupnodejs @
categoriesnodejs
postedSep 18, '12 at 11:28a
activeSep 28, '12 at 3:22p
posts5
users3
websitenodejs.org
irc#node.js

People

Translate

site design / logo © 2022 Grokbase