Silly http benchmark

[Cuper Hector]

Hi Justin,

I found another benchmark test of Netty HTTP:
http://timyang.net/programming/c-erlang-java-performance/

Netty performs pretty well in the benchmark.


On Fri, Jan 29, 2010 at 11:27 AM, "Trustin Lee (이희승)" <trustin at gmail.com>wrote:

> Hi Luis,
>
> First off, thank you very much for spending significant amount of time
> for running performance tests.  This is a great news for the community
> absolutely. :)
>
> I'd like to add your performance report to the project web site if you
> don't mind:
>
>    http://jboss.org/netty/performance.html
>
> I think it's fine to publish it as long as it is easily reproduceable as
> written in your instruction and each test did not fail.  Perhaps you
> could send me the full test log files then I could upload it together.
>
> Also, could you try to run the test with the latest build and publish
> the result again?  I have done significant performance optimization
> which might yield better throughput in some situation.  Get the latest
> build here:
>
>    http://hudson.jboss.org/hudson/view/Netty/job/netty/2531/
>
> Cheers,
> Trustin
>
> Luis Neves wrote:
> > Thought I would share the results of a silly http benchmark of netty
> > against the competition.
> > To keep thinks interesting I added the nginx http server to the mix to
> > get an idea of how Java server compares to a highly optimized C
> > server.
> >
> > Nginx has a module called  "empty_gif" that serves a 1x1 transparent
> > gif directly from memory which is perfect for this purpose.
> > I used the exact same gif for all the Java servers.
> >
> > Both the client and the server machines are quad cores running Linux
> > 2.6.31 that are linked via a 1GB switch.
> >
> > I used ab as the testing tool with 4 parallel processes. The testing
> > script is as follows:
> >
> > *******************************************************************
> >
> > #!/bin/bash
> >
> > set -e
> > cd $(dirname $0)
> > rm -fv *.log
> >
> > for i in $(seq 1 4); do
> > ab -c500 -n1000000 -k -S -r -d http://<host>/bench > $i.log &
> > done
> >
> > wait
> >
> > cat *.log | grep Requests | awk '{ sum+= $4 } END {printf "\n\n
> > Average requests per second: %8.2f\n\n",sum}'
> > *******************************************************************
> >
> >
> > As you can see it's not a very scientific method :-) ... anyway, each
> > of the ab processes creates 500 connections and makes 1000000
> > keep-alive requests.
> > The average results across several runs were:
> >
> > mina (trunk) - 25K req/sec
> > grizzly (1.9.18-i)- 55K  req/sec
> > netyy (3.2-ALPHA3) - 80K req/sec
> > nginx - 115K req/seq
> >
> >
> > Impressive results for Netty I think.
> > The code used is available here:
> > <http://dl.dropbox.com/u/279023/netty/http_test.tar.gz>
> >
> > If there is something wrong with it please let me know.
> >
> >
> > --
> > Luis Neves
> > _______________________________________________
> > netty-users mailing list
> > netty-users at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/netty-users
>
> --
> what we call human nature in actuality is human habit
> http://gleamynode.net/
>
>
>
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/netty-users/attachments/20100129/f9a69519/attachment.html