Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of i.galic@brainsware.org
 designates 188.40.115.121 as permitted sender)
Date: Tue, 15 Jun 2010 21:23:41 +0000 (UTC)
From: =?utf-8?Q?Igor_Gali=C4=87?= <i.galic@brainsware.org>
To: dev@httpd.apache.org
Message-ID: <82251847.341.1276637021681.JavaMail.root@iris>
In-Reply-To: <4C17ED72.6000100@kippdata.de>
Subject: Re: MPM default config and conf/extra/httpd-mpm.conf
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


> >
> > I wonder if this thread is wrong enough for the topic:
> >
> > Would it be possible to choose defaults for the MPMs based on
> > the available CPU(core)s and the Memory, rather than just hard
> > coding the values?
>=20
> I doubt it's worth it and that we can make it work nicely. I think we
>=20
> are looking for a mid-size configuration that neither optimizes on
> tiny=20
> systems (saving as much resources as possible) nor on high load
> systems=20
> (extreme scaling) but instead for the huge number on configurations in
>=20
> between, that hope to work reasonable with default sizing.
>=20
> If we are talking about auto-detecting system resources: Memory and
> CPU=20
> in these cases often is not only used for httpd because it is not the
>=20
> only application on the system.
>=20
> If we want the user to assign those resources I doubt we can find good
>=20
> formulas.

ACK.
Then it's probably best to set sane defaults which will work well
and work well everywhere.
In the config we could then provide hints how to scale it up or down.
=20
> Rainer

Bye
--=20
Igor Gali=C4=87

Tel: +43 (0) 699 122 96 338
Fax: +43(0) 1 91 333 41
Mail: i.galic@brainsware.org
URL: http://brainsware.org/