On Thu, Aug 23, 2012 at 7:34 AM, jason.桂林 <[email protected]> wrote: > test by node.js http helloworld > > 10 concurrent connections > response: 0ms(min) 19ms(max) 1ms(avg) > > 30 concurrent connections > response: 2ms(min) 20ms(max) 4ms(avg) > > 100 concurrent connections > response: 7ms(min) 43ms(max) 15ms(avg) > > 1000 concurrent connections > response: 6ms(min) 212ms(max) 167ms(avg) > > > We can see that, node.js response time increased with concurrent > connections, any one can explain this? > > And how to avoid this problem, and if it is not http but tcp, will it be an > critical issue for multi player online game server, there will be many > concurrent connections.
Your post omits crucial details, like on what OS you tested it, on what kind of network, with what tool, what the tool's settings were, etc. All one can say by the numbers posted is that the response time seems to scale linearly - which isn't all that bad, really. -- 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
