Closed serby closed 12 years ago
If other benchmarked processes take advantage of multicore/cpu arch, then definitely this needs to happen.
Serby how about we nodejs guys fork and do it ourselves and pull back. I'm eager to see the results of round 2.
You might want to try node while disabling V8's garbage collector by passing this to node –nouse-idle-notification
einaros submitted a clustered implementation of the ws server: https://github.com/ericmoritz/wsdemo/pull/23
I am rerunning the benchmark now. I'll let you know.
I couldn't use the data for the benchmark I ran a day ago. I stopped the AWS instances and when I started them back up I got a different box and with it different performance characteristics.
I am working on automating the benchmarking so that I don't have to babysit it. I should be able to rerun the entire suite then weekend.
If you are going to run on a 64bit m1.large machine then you need to add cluster support to the node.js test so it can fork a process for each CPU.
http://nodejs.org/docs/latest/api/cluster.html