On Thu, 27 May 2004 14:18:02 +0900, Jim Freeze wrote
 
> test.rhtml - webrick w/o fastcgi
>  Concurrency Level:      1
>  Time taken for tests:   10.221 seconds
>  Complete requests:      100
>  Requests per second:    9.78 [#/sec] (mean)
>  Time per request:       102.21 [ms] (mean)

Wow.  That seems awfully slow, especially for your hardware.

I did this test on a PIII 800 Mhz w/ 512Mb running Gentoo Linux that was 
also running a full X desktop with Eclipse and a bunch of other stuff open 
at the time.

The test content was 4454 bytes long.  All concurrency levels were 1.  I ran 
each test over 100 requests, and did it 3 times.  The number reported are 
the results of the third run.

Webrick serving content via a cgi:
  6.26 requests per second

Webrick serving the exact same content as a static HTML file:
  54.90 requests per second

Iowa behind Apache 1.3.29 using a mod_ruby handler for communication, 
serving the same static content:
  72.12 requests per second

Iowa, same configuration, serving the original content which includes 
several components and dynamic content generation:
  35.70 requests per second

Same combination, but with FastCGI instead of mod_ruby:
  37.70 requests per second (interesting, since in some earlier tests, the 
FCGI combo was 1-2 requests per second slower).

I was a bit surprised the Iowa was faster than Webrick at serving the static 
content, though I suppose by allowing Apache to handle the front end of the 
interaction with the browser, Iowa gets to skip out on a lot of the work 
that Webrick has to do before the content gets delivered.

I'm eager to run this same test with Webrick/Iowa integration.  I'm hopeful 
that it will be close to the Apache/Iowa via mod_ruby combination.


Kirk Haines