On Sun, Jan 2, 2011 at 4:31 PM, Guy Royse <[email protected]> wrote: > So how does node.js work with multi-core processors.
The core language itself does not. But there are add-ons that do. See https://github.com/kriszyp/multi-node and http://stackoverflow.com/questions/2387724/node-js-on-multi-core-machines Also, I must confess to being a bit of a node.js geek, myself. Earlier in the year, I did some testing with a simple "hello world" script on our old dev server (a quad core Xeon, don't remember the clock speed). Even with one core running node.js, I used Apache Benchmark to hammer that instance with 1000 concurrent connections and saw 3,500 requests a *second*. High levels of concurrency like that are one of the things that make async I/O so powerful, and one of the reasons why so many people are paying attention to node.js. I honestly don't think you could see that kind of performance with 1,000 separate threads/child processes. If folks are at all interested (and the modes here think it's on topic), I'd be happy to run some node.js benchmarks on other platforms (Macs, and Amazon EC2) and post the results here, perhaps along with some sample code. -- Doug -- Douglas T. Muth * Philadelphia, PA, USA http://www.dmuth.org/ http://twitter.com/dmuth -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
