Anyone argue with this can make a test on it. I am test on MacOSX, benchmark tool is write in node.js.
在 2012-8-24，上午11:25， Matt 写道： > This is not a correct response. If you hit the open file limit usually node > will crash (unless you protect against that). It won't ever slow down because > of it. And it won't ever just pause connections until the limit is lowered. > It will throw an error or an exception. > > On Thu, Aug 23, 2012 at 8:58 PM, Murvin Lai <[email protected]> wrote: > this is normal because you are running with default 1024 open file limit. > > As the socket pool is limited to 1024 sockets, and you have 1000 concurrent > requests, requests will be accumulated in the socket queue and thus, have to > wait unitl other requests are done from the pool and released. > > easy way is to change the /etc/security/limits.conf file and increase the > open file soft/hard limit. Once you increase that, you will be fine with > 1000 concurrent requests. > > but there are other factors and will overwrite the limit. please see my > website for tips... murvinlai.com > > > On Thu, Aug 23, 2012 at 3:51 AM, Ben Noordhuis <[email protected]> wrote: > 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 > > > -- > 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 > > > -- > 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 -- 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
