Hi Philip,

On vrijdag, apr 1, 2005, at 20:21 Europe/Amsterdam, [EMAIL PROTECTED] wrote:

On 25-Mar-2005 Bas Schulte wrote:
What are your experiencess with PoCo::Server:: HTTP as webapp server
and what is the type of traffic/connections per second that it handles?

I use PoCo::Server::HTTP in a low traffic environment. However, using it
and my PoCo::Deamon module in pre-forking mode produces the following
results.


Serving up inline content.  That is, content generated with :

    $response->content(<<HTML);
... HTML HERE ...
HTML

ab -n 1000 -c 20 http://dw-2:33100/

Requests per second: 40.82 [#/sec] (mean)
Time per request: 489.90 [ms] (mean)
Time per request: 24.50 [ms] (mean, across all concurrent requests)


Server is a Celeron 2.8Ghz, with 256Mb RAM.  Load was 0.40.

Serving static content from a file.

ab -v 1 -n 1000 -c 20 http://dw-2:33100/static/stylee.css

Requests per second: 41.76 [#/sec] (mean)
Time per request: 478.92 [ms] (mean)
Time per request: 23.95 [ms] (mean, across all concurrent requests)
Transfer rate: 413.97 [Kbytes/sec] received


Server is a Celeron 2.8Ghz, with 256Mb RAM. Load was 0.70.

Thanks for the details!

To be honest, I think these numbers are somewhat disappointing, I recall (I'm getting old ;)) stats from Apache serving static content in the 300/reqs per seconds range and I've seen peaks on our Apache/mod_perl "application server" (stripped Apache, mod_perl, with one mod_perl handler executing commands) of around 50/s. That was based on input on production servers, never really had the time to see where the max. was.

For me, it's no problem: the POE-based daemon I wrote won't be handling more than max. 10 reqs/second for the foreseeable future.

I'm just toying with the idea of replacing our app server with something POE-based, but it might not be worth it. Apache/mod_perl "just works", except for the extra hassles to share data and control concurrency between Apache children. I think I could come up with a more elegant approach using POE on that subject (sharing data/concurrency control etc.) but if I won't get more than 40 reqs/second, that elegance isn't worth it.

Cheers,

Bas.



Reply via email to