Message-Id: <199606181426.KAA23022@breckenridge.openmarket.com>
To: fastcgi-developers@openmarket.com
Subject: mod_fastcgi performance problem
Date: Tue, 18 Jun 1996 10:26:33 -0400
From: Mark Brown <mbrown@openmarket.com>
Here is some information on how to set the select
timeout in mod_fastcgi.
--mark
------- Forwarded Message
To: Mark Brown <mbrown@openmarket.com>
Subject: Re: Fastcgi and cookies
In-Reply-To: Your message of "Mon, 17 Jun 1996 15:52:00 EDT."<199606171952.PAA20884@breckenridge.openmarket.com>
Date: Mon, 17 Jun 1996 23:19:43 -0700
From: Doug Urner <dlu@wobble.albatross.com>
>Speaking of performance, a message went by yesterday on the Apache
>list reporting a serious performance bug in mod_fastcgi. The select
>call in mod_fastcgi is specified to use a zero timeout; a much
>longer timeout (perhaps infinite) would be appropriate.
>As soon as we have a good patch it will go to this list.
An infinite timeout doesn't work . . .
I've experimenting in the 5000 to 10000 msec range with good results
(almost as fast as NSAPI), with the zero timeout it was SloooowCGI :-(
I'm not sure why the infinite timeout doesn't work, but it seems to
cause the server to hang.
Doug
- --
Douglas L. Urner, dlu@bsdi.com, +1.503.231.4881
------- End of Forwarded Message