Raw data looks to have a problem

Question

Raw data looks to have a problem

devonjones opened this issue 12 years ago · comments

Your writeup for the websockets 10k connection demo seems to have a problem. Java and Haskell have connections + connection timeouts == 5000, but for all other languages connections + connection timeouts == 10000. I suspect that the java and haskell versions were running the older 5k test.

Eric Moritz · Answer 1 · Mon Jun 18 2012 05:46:23 GMT+0800 (China Standard Time)

They both say

Running test with 10000 clients for 300 seconds

In the client's output. I've ran this benchmark a few times and most of the servers exhibit the same behavior of crapping out around 5000-7000 clients. I don't know what the cause is.

Devon Jones · Answer 2 · Mon Jun 18 2012 06:20:12 GMT+0800 (China Standard Time)

I did notice that on the top, but down in the content, it says:
Java:
{connections,4637},
{disconnections,0},
{messages,1028390},
{connection_timeouts,157},

Haskell:
{connections,4996},
{disconnections,0},
{messages,1187413},
{connection_timeouts,108},

so there's definitely a discrepancy between the top of the client's output and the body.

Eric Moritz · Answer 3 · Mon Jun 18 2012 06:46:22 GMT+0800 (China Standard Time)

Yeah, I'm not sure what that is. I noticed that myself Not sure why that is. I made the assumption was that the server opened the TCP connection but hung on the handshake. I should probably log a handshake_started event that occurs when the connection is opened to be able to prove that assumption.