Geek Answers Handbook

Are there any tests showing how many comet requests per second can be processed with Node.js 0.6.8?

The reason I'm asking is post

http://amix.dk/blog/post/19577

Indicates that Node.js 0.2.2 seems to have a threshold of 500 / s and exceeds 10x Netty. In the comments, Ryan Dahl points out that this is possible due to an error that was subsequently fixed. However, I cannot find in the rest of the message or elsewhere any confirmation that the problem has been resolved, and if so, the standards have been updated. We currently have many versions earlier than above, and I wonder if there are any tests, formal or otherwise, related to comet / second requests.

If there are no benchmarks, it would be good to know in general terms whether the problem noted by Amir remains unfulfilled. 500 comets / second is a threshold value that can be reached using a site with a limited chat / game size.

+5
source share
1 answer

node.jscome a long way from 0.2.2. There were probably problems with the implementation of the architecture discussed in the related entry, as the comments suggest that they did not consider using multiple node processes with a load balancer.

This is clearly necessary for high-performance applications - indeed, the last paragraph of the node.js official section reads:

concurrency? ? child_process.fork(), . .

, , node 0.2.2 % 10 Netty ( OP ), 10 node , : Netty 10 , node, 10x , ? , node >=0.6.0, Windows, . . Windows 0.6.0 :

http 600 10GE , .

                            v0.4.12 (windows)   v0.6.0 (windows)
http_simple.js /bytes/1024  3858 r/s            5823 r/s
io.js read                  12.41 mB/s          26.51 mB/s
io.js write                 12.61 mB/s          33.58 mB/s
startup.js                  152.81 ms           52.04 ms

, , , , , , node.js . Google, Yahoo, Mozilla, LinkedIn i.TV Node enterprisebeat.com.

/, , , 500.

+2

More articles:


All Articles