Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: Inadequate hosting for www.postgresql.org
Date: Wed, 3 Nov 2004 08:44:32 -0000
Message-ID: 
 <E7F85A1B5FF8D44C8A1AF6885BC9A0E4306F82@ratbert.vale-housing.co.uk>
Thread-Topic: [pgsql-www] Inadequate hosting for www.postgresql.org
Thread-Index: AcTBRCWfs1us8azmRvWC2t0DaZGxhQAPGpXw
From: "Dave Page" <dpage@vale-housing.co.uk>
To: "Oleg Bartunov" <oleg@sai.msu.su>,
	"Marc G. Fournier" <scrappy@postgresql.org>
Cc: "Alexey Borzov" <borz_off@cs.msu.su>, <pgsql-www@postgresql.org>

=20

> -----Original Message-----
> From: Oleg Bartunov [mailto:oleg@sai.msu.su]=20
> Sent: 03 November 2004 01:26
> To: Marc G. Fournier
> Cc: Alexey Borzov; Dave Page; pgsql-www@postgresql.org
> Subject: Re: [pgsql-www] Inadequate hosting for www.postgresql.org
>=20
> Its interesting to see how webperf.org sees different=20
> postgresql.org pages. For example,

<snip stats>

Yes, that is interesting. What's even more interesting is running the
stats on www.postgresql.org/index.php. All of a sudden, it becomes
apparent that the servers isn't doing a bad job serving static HTML,
it's the PHP stuff that's dog slow.

> But, I again want to  stress that current architecture of=20
> postgresql.org sites are very-very bad and you will never get=20
> nice performance and scalability especially for dynamic sites without:

Agreed, but I think there's a more fundamental problem to fix before
getting down to the level of optimisation you suggest.

Regards, Dave.