Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: PostgreSQL web site
Date: Mon, 28 Aug 2006 21:48:19 +0200
Message-ID: <6BCB9D8A16AC4241919521715F4D8BCEA0FB7F@algol.sollentuna.se>
In-Reply-To: <44F34549.7040400@commandprompt.com>
Thread-Topic: [pgsql-www] PostgreSQL web site
Thread-Index: AcbK2P/1iTKMFVxhQySXzBdKMiHynAAAc12w
From: "Magnus Hagander" <mha@sollentuna.net>
To: "Joshua D. Drake" <jd@commandprompt.com>,
	"Naz Gassiep" <naz@mira.net>
Cc: "John Hansen" <john@geeknet.com.au>, <pgsql-www@postgresql.org>

> >> index.html
> >> index.html.gz
> >>
> >> etc...
> >>
> >>  =20
> > Oh, thats a bad idea, I think, as it would hugely increase the=20
> > maintenance work on the site, for a marginal gain in server=20
> > performance. The load increase really is minimal. If our=20
> servers are=20
> > so close to breaking point that this is an issue then we'll=20
> need new ones very soon anyway.
>=20
> Yeah... no. Mod_deflate will allow auto-negotiation so that=20
> the information can be dealt with either way. No reason to=20
> increase the workload.

We're nowhere near the load that our static servers can deliver. Even
during release time, when it increases sometimes hundredfold.
That doesn't mean we shouldn't optimize when we can do so at trivial
cost, though.

//Magnus