Caucho Resin: faster than nginx?

Sat Aug 18 03:17:27 UTC 2012

On Saturday 18 August 2012 03:18:32 Adam Zell wrote:
> FYI:
> http://www.caucho.com/resin-application-server/press/resin-java-web-server-
> outperforms-nginx/
> 
> 
> " Using industry standard tool and methodology, Resin Pro web server was
> put to the test versus Nginx, a popular web server with a reputation for
> efficiency and performance. Nginx is known to be faster and more reliable
> under load than the popular Apache HTTPD. Benchmark tests between Resin and
> Nginx yielded competitive figures, with Resin leading with fewer errors and
> faster response times. In numerous and varying tests, Resin handled 20% to
> 25% more load while still outperforming Nginx. In particular, Resin was
> able to sustain fast response times under extremely heavy load while Nginx
> performance degraded. "

What nginx configuration was used during the testing? Did they tune it?
Did Resin use an equivalent level of logging? What build options were used
to build nginx? Why did they test on 1k page? I don't think that the average
size of typical web-page and its elements are about 1 Kb. Does it mean that
the Resin cannot effectively handle files of more size? What about memory
usage? And after all, why did they use the latest version of Resin and
relatively old version of nginx?

 wbr, Valentin V. Bartenev

P.S.

vbart at vbart-laptop ~/Development/Nginx/tests/wrk $ curl -i http://localhost:8000/1k.html
HTTP/1.1 200 OK
Server: nginx/1.3.5
Date: Sat, 18 Aug 2012 03:10:13 GMT
Content-Type: text/html
Content-Length: 1063
Last-Modified: Sat, 18 Aug 2012 02:40:43 GMT
Connection: keep-alive
ETag: "502f00ab-427"
Accept-Ranges: bytes

<html>
<body>
<pre>
0 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 
1 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 
2 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 
3 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 
4 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 
5 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 
6 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 
7 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 
8 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 
9 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 
</pre>
</body> 
</html>
vbart at vbart-laptop ~/Development/Nginx/tests/wrk $ cat ../build/test.conf
#error_log  logs/error.log debug;

worker_processes     2;
worker_priority     -5;
worker_cpu_affinity  1000 0010;

events {
    accept_mutex off;
}

http {
    sendfile on;
    access_log off;
    tcp_nopush on;

    open_file_cache max=16;
    open_file_cache_valid 1h;

    server {
        location / { }
    }
}
vbart at vbart-laptop ~/Development/Nginx/tests/wrk $ grep "model name" /proc/cpuinfo | uniq
model name      : Intel(R) Core(TM) i3 CPU       M 350  @ 2.27GHz
vbart at vbart-laptop ~/Development/Nginx/tests/wrk $ ./wrk -r 3m -c 10 -t 1 --pipeline 100 http://localhost:8000/1k.html
Making 3000000 requests to http://localhost:8000/1k.html
  1 threads and 10 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     5.79ms   50.47us   6.03ms   75.42%
    Req/Sec   170.72k   450.75   171.00k    72.03%
  3000005 requests in 17.54s, 3.63GB read
Requests/sec: 171078.30
Transfer/sec:    212.25MB