Hi Nuno, You can think of threadjs as a cluster module that works on threads instead of processes and focus on high performance networking. Currently, it just provides a limited module system to run on the thread. But you can dispatch works to nodejs and that leaves threadjs just a network engine.
As of the benchmarks, the line net connection/sec means "use net module and benchmark in one request per connection mode i.e. http/1.0 method" net keepalive request/sec means "use net module and benchmark in one connection many requests mode i.e. http/1.1 keepalive method" and http connection/sec http keepalive request/sec get the same meaning but just use http module for the benchmarks. node_cluster: means to use nodejs cluster module for the benchmark. node with tj: means to use threadjs but pass javascript code back to nodejs. threadjs: means to use threadjs and runs javascript on threads. And the first column of the data means the concurrent connections number. i.e. the -n xxxx parameter of the benchmark tool. Hope this helps. Thanks, Robert On Thursday, September 20, 2012 9:28:36 PM UTC+8, Nuno Job wrote: > > Can you provide a better explanation of what the project his, and what the > benchmarks refer to? > > I was curious to understand but didn't really grasp it with the email you > sent alone. :) > > Nuno > -- 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
