From: Brian Candler <B.Candler@...>
Date: 2004-11-02T20:20:37+09:00
Subject: Re: fastcgi performance problems and ruby

> cgi.out{content}

I think that may be your problem. The 'out' methods of cgi are inefficient,
I believe due to the large number of singleton methods which are added on
each object - although I seem to remember it's much worse if you do
each_cgi("html3") for example.

As suggested elsewhere, try rewriting your app to use the native fastcgi API
(each) rather than each_cgi.

Also, if your benchmarks are forcing a lot of concurrent connections, then
you could try configuring mod_fastcgi to launch a static pool of processes
for your application (say 5 or 10 processes) to see if that zips things
along, because in that case they will be pre-spawned.

Regards,

Brian.