Hi everybody. As you may know from my previous posts, I'm stress
testing a node.js server using another node.js server as client
(through http.request). My problem is simple: when I start my tests
with 100 to 1000 clients contacting the same server I notice that
while the vast majority of them terminates (90% to 99%) there are a
small part of those that doesn't terminate: by doing a ps aux | grep
node I can see that those clients are still running, thus are waiting
for response from the server. Since I set a timeout for the incoming
connections in the server (same timeout for outgoing connections in
the client) I should wait up to 20 minutes (that's the timeout) to
read an error message telling me that the socket connection was
closed. I haven't waited that much time in reality but I'm pretty sure
the result will be that.

My question is: where did this small percentage of clients got lost? I
can see the log of the server and after the majority of connections
finishes, the server doesn't log anything else, like it's not
receiving anything. My thought is that the server lost some connection
while dealing with the others. The server is not simply answering with
hello world, it's performing operations and connecting to a database.
Moreover every client does more than one connection to the server
(once one finishes another one starts, it's the flow of my
application, at least 2 connections per client).

What do you guys think?

Masiar

-- 
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

Reply via email to