On Wed, Apr 23, 2003 at 10:51:02AM +0100, Colin Watson wrote:
> On Wed, Apr 23, 2003 at 10:20:48AM +0200, Josip Rodin wrote:
> > On Wed, Apr 23, 2003 at 01:50:26AM +0200, Frank Lichtenheld wrote:
> > > It's disk space against cpu usage. Clearly the first is much
> > > cheaper.
> >
> > Perhaps I should also mention the exact cause of those 500 errors that
> > was briefly mentioned on -www recently -- the MaxClients 300 setting
> > on gluck exceeds the maxproc 256 setting. Of course, this is a bug,
> > and it will be fixed, but this still means that apache on the machine
> > often runs two hundred processes as it is, so adding more CGIs/PHPs
> > wouldn't exactly be the happiest solution.
>
> Sane performance tuning strategies dictate that more stuff should be
> in-process, then. Is mod_perl feasible?
Or libapache-mod-speedycgi if there's enough spare RAM available.
/me hides
--
Jose Carlos Garcia Sogo
jsogo@debian.org
Attachment:
pgpBEUNiFq4U2.pgp
Description: PGP signature