Hi Trustin,<div><br></div><div>I've not made the HttpCore/NIO vs Netty benchmark yet, but I'm doing instead some more benchmarks, using 'ab' this time. I also get quite often this error, again when the -C parameter is over 2500: </div>
<div><br></div><div><div><font class="Apple-style-span" face="'courier new', monospace">>> ab -n10000 -c3000 '<a href="http://69.164.208.81:8000/">http://69.164.208.81:8000/</a>'</font></div><div><font class="Apple-style-span" face="'courier new', monospace">Completed 1000 requests</font></div>
<div><font class="Apple-style-span" face="'courier new', monospace">Completed 2000 requests</font></div><div><font class="Apple-style-span" face="'courier new', monospace">Completed 3000 requests</font></div>
<div><font class="Apple-style-span" face="'courier new', monospace">Completed 4000 requests</font></div><div><font class="Apple-style-span" face="'courier new', monospace"><b>apr_socket_recv: Connection reset by peer (104)</b></font></div>
<div><font class="Apple-style-span" face="'courier new', monospace">This is ApacheBench, Version 2.3 <$Revision: 655654 $></font></div><div><font class="Apple-style-span" face="'courier new', monospace">Copyright 1996 Adam Twiss, Zeus Technology Ltd, <a href="http://www.zeustech.net/">http://www.zeustech.net/</a></font></div>
<div><font class="Apple-style-span" face="'courier new', monospace">Licensed to The Apache Software Foundation, <a href="http://www.apache.org/">http://www.apache.org/</a></font></div><div><font class="Apple-style-span" face="'courier new', monospace"><br>
</font></div><div><font class="Apple-style-span" face="'courier new', monospace">Benchmarking 69.164.208.81 (be patient)</font></div><div><font class="Apple-style-span" face="'courier new', monospace">Total of 4123 requests completed</font></div>
</div><div><br></div><div>and at some point when -C=6000), all connections are properly processed. So it's likely to be a sytem configuration problem, but then at some point the Netty server becomes unresponsive.</div>
<div><br></div><div>Would you have some tips on how to find the reason for the connection reset and also on how to detect (from the Netty server) that Netty becomes unresponsive ?</div><div><br></div><div>Thanks,</div><div>
<br></div><div> -- Sébastien<br><br><div class="gmail_quote">2010/1/6 "Trustin Lee (이희승)" <span dir="ltr"><<a href="mailto:trustin@gmail.com">trustin@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Sébastien,<br>
<br>
You might be running out of available ports due to many TIME_WAIT either<br>
on the client or server side. Could you confirm it? If so, you need to<br>
wait until the TIME_WAIT state is cleared between each run.<br>
<br>
If HttpCore/NIO version works fine when Netty fails, I'd like to compare<br>
the two to see what the differences are. Please paste or attach the<br>
source code.<br>
<br>
Thanks,<br>
Trustin<br>
<div><div></div><div class="h5"><br>
Sébastien Pierre wrote:<br>
> Hi there !<br>
><br>
> I just moved a test HTTP service from HttpCore/NIO to Netty based on the<br>
> HTTP snoop example. I experienced (despite good performance at first) that<br>
> the server is dropping connections when the load is heavy. To reproduce<br>
> this, simply start the snoop example:<br>
><br>
> java -cp ./src/main/java/:./jar/netty-3.2.0.ALPHA2.jar<br>
> org.jboss.netty.example.http.snoop.HttpServer<br>
><br>
> and then do<br>
><br>
> python -c'for r in range(500,10500,500): import os ; os.system("httperf<br>
> --hog --timeout=60 --client=0/1 --server=127.0.0.1 --port=8080 --uri=/<br>
> --rate=%s --send-buffer=4096 --recv-buffer=16384 --num-conns=10000<br>
> --num-calls=1" % (r))'<br>
><br>
> which is the same as running this command with --rate growing from 500 to<br>
> 10000 with 500 increases.<br>
><br>
> httperf --hog --timeout=60 --client=0/1 --server=127.0.0.1 --port=8080<br>
> --uri=/ --rate=500 --send-buffer=4096 --recv-buffer=16384 --num-conns=10000<br>
> --num-calls=1<br>
><br>
> so in this example, Netty often drops connections between rates of 3000 and<br>
> 5000, which you'll see in httpperf's log with the following lines:<br>
><br>
> httperf: connection failed with unexpected error 98<br>
> ...<br>
> Errors: total 2236 client-timo 0 socket-timo 0 connrefused 0 connreset 0<br>
> Errors: fd-unavail 0 addrunavail 0 ftab-full 0 other 2236<br>
><br>
> I attached a graph where you'll see that for the rate=4000 and rate=45000<br>
> the server just dropped all the connections (from httperf's perspective at<br>
> least). So do you know any way to prevent or at least detect that ?<br>
><br>
> Thanks !<br>
><br>
> -- Sébastien<br>
><br>
> PS: I should add that I've run the test a couple of times, and quite often<br>
> have trouble in the rate=3000-5000 range<br>
><br>
><br>
><br>
</div></div>> ------------------------------------------------------------------------<br>
><br>
> _______________________________________________<br>
> netty-users mailing list<br>
> <a href="mailto:netty-users@lists.jboss.org">netty-users@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/netty-users" target="_blank">https://lists.jboss.org/mailman/listinfo/netty-users</a><br>
<font color="#888888"><br>
--<br>
what we call human nature in actuality is human habit<br>
<a href="http://gleamynode.net/" target="_blank">http://gleamynode.net/</a><br>
<br>
<br>
</font><br>_______________________________________________<br>
netty-users mailing list<br>
<a href="mailto:netty-users@lists.jboss.org">netty-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/netty-users" target="_blank">https://lists.jboss.org/mailman/listinfo/netty-users</a><br>
<br></blockquote></div><br></div>