On Mar 25, 5:18 pm, Brad Carleton <[email protected]> wrote: > So here at request number 699, you see the response time jump by about > 2500ms. The "response time" is what the load tester reads and the > "time spent on server" is what the server under test reports as its > time spent on the request. Obviously, I realize that if the CPU is > busy requests will queue up, but is there any way to get insight into > this? Is this a problem with TCP tuning on my linux instance? I have > max connections for the instance set to 20,000.
Could you post the code you're using to gist.github.com and describe what you're using for creating the concurrent connections (node, ab, etc)? -- 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
