I think what you're seeing is a micro benchmark effect, that is all you're measuring is how fast messages can be sent, which is very fast but could easily depend in some way on the number of workers. A more realistic benchmark would have each worker do something relatively expensive (compared to sending a message) on each message. I did that here using some old trig benchmark from sunspider as the "work":
https://gist.github.com/femto113/5202935 This now reports both "message sending rate" and "work accomplished rate". I'm guessing in general a higher work rate is the real value of a cluster. Interestingly on my quad-core Mac I seem to get the best work rate with 2 workers (and it pegs all four cores). -- -- 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 --- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
