I ran this code as-is on Ubuntu and was able to see it hitting all cpus, using weighttp to hit the cluster and htop to monitor cpu usage and processor assignment.
It appears you may be running this on windows (given your load utility choice) though, sorry I can't help with that. -John On Fri, Jan 3, 2014 at 10:46 AM, Jason Shinn <jmsh...@gmail.com> wrote: > I've not tried anything like this, or worked with cluster at all, but the > first thing I would try is to remove the setupServer abstraction and put > the server setup code directly in the worker block. That appears to be how > all of the examples I'm seeing are set up. Specifically, the nature of how > node allows the sharing of TCP connections between workers may require that > code to be defined in the worker block. > > Again, I haven't actually tried this, so I may be off base, but it's a > simple thing to try. > > > On Friday, January 3, 2014 12:47:13 PM UTC-5, Peter Hsu wrote: >> >> Thanks you Sam! >> >> I am generating load from a different client machine. I tried 2 clients >> and same CPU utilization appears on the server side, so I am currently >> ruling out insufficient load. I am generating load using wcat ( >> http://www.iis.net/downloads/community/2007/05/wcat-63-(x64) ). My >> nodejs is v0.10.24 x64 >> >> On Thursday, January 2, 2014 8:51:32 PM UTC-8, Sam Roberts wrote: >>> >>> I've written code like this and saturated cores. >>> >>> I wonder... are you running your benchmark client on same machine as >>> node? Is it possible that your benchmark client is single-threaded, >>> and is basically saturating a single CPU trying to hit node as fast as >>> it can, and node is running so fast on the other CPUs that all you see >>> is the load-generator on its CPU? >>> >>> If that is not the case, node version, system, and how you are >>> generating load, all would be useful. >>> >>> Sam >>> >> -- > -- > 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+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > > --- > 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 nodejs+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- John R. Fitzgerald -- -- 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- 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 nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
