I don't think this is a problem. Problem should occur when the response time is in SECONDS like 3-4 second.
I really think nodejs can handle millions of concurrent users on a good server. Read this , http://blog.caustik.com/2012/04/10/node-js-w250k-concurrent-connections/ On Thursday, August 23, 2012 11:04:31 AM UTC+5:30, Jason.桂林(Gui Lin) 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. > > -- > Best regards, > > 桂林 (Gui Lin) > > guileen@twitter <https://twitter.com/#!/guileen> > 桂糊涂@weibo <http://weibo.com/guileen> > guileen@github <https://github.com/guileen> > > -- 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
