X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id E4EBB3A47FB;
	Thu,  4 Nov 2004 05:26:53 +0000 (GMT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 10262-02; Thu,  4 Nov 2004 05:26:44 +0000 (GMT)
Received: from lon-mail.telstra.net (unknown [203.50.2.188])
	by svr1.postgresql.org (Postfix) with ESMTP id AABE93A46D4;
	Thu,  4 Nov 2004 05:26:43 +0000 (GMT)
Received: from [203.50.0.197] (rsdhcp5.telstra.net [203.50.0.197])
	by lon-mail.telstra.net (8.12.11/8.12.8) with ESMTP id iA45Qctp052801;
	Thu, 4 Nov 2004 16:26:38 +1100 (EST)
	(envelope-from justin@postgresql.org)
Message-ID: <4189BD89.7020403@postgresql.org>
Date: Thu, 04 Nov 2004 16:26:33 +1100
From: Justin Clift <justin@postgresql.org>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Marc G. Fournier" <scrappy@postgresql.org>
Cc: pgsql-www@postgresql.org, ale@freebsd.org
Subject: Re: Inadequate hosting for www.postgresql.org
References: 
 <E7F85A1B5FF8D44C8A1AF6885BC9A0E4306FBC@ratbert.vale-housing.co.uk>
	<330532b6041103143870f5a6d2@mail.gmail.com>
	<41895FF2.10709@ehpg.net> <20041103202855.Y82047@ganymede.hub.org>
	<330532b6041103164743857939@mail.gmail.com>
	<20041103205945.R82047@ganymede.hub.org>
	<330532b604110317243f079b55@mail.gmail.com>
	<20041103215500.O82047@ganymede.hub.org>
	<20041103221933.F82047@ganymede.hub.org>
	<4189B0D4.3040809@postgresql.org>
	<20041104004958.B82047@ganymede.hub.org>
In-Reply-To: <20041104004958.B82047@ganymede.hub.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests=
X-Spam-Level: 
X-Archive-Number: 200411/88
X-Sequence-Number: 5819

Hi Marc,

Ok, I've CC'd the listed maintainer of the FreeBSD PHP port on this so 
that he finds out the --enable-versioning option may be causing some 
performance problems.

Wonder if he's aware of it already at all?

:-/

Regards and best wishes,

Justin Clift


Marc G. Fournier wrote:
> On Thu, 4 Nov 2004, Justin Clift wrote:
> 
>> Marc G. Fournier wrote:
>> <snip>
>>
>>> You might have hit it on the mark:
>>
>> Um, now I'm lost.  Recompiling the main PHP binary without 
>> --enable-versioning was the winner?
> 
> 
> Ya ... I think what happens is that when the main php starts up, the 
> first thing it does is goes through its 'extensions' to make sure they 
> are part of the same version ... *why* it would do it each and ever 
> connection, vs just when apache starts up, I don't know ... but, I'm on 
> a dial-up link at home and I can actually load wwwdevel.postgresql.org 
> now, where before I had enough time to go to the kitchen for a drink 
> waiting for it to load ...
> 
> But, I also don't believe it was *just* that option ... the database was 
> slow, due to the need for the vacuum full, which was apparent with the 
> load times on the current site ...
> 
> But, after upgrading and restarting apache on all the VMs, with the 
> change to PHP, even the servers loadavg are all back down to 'normal' ...
> 
> What I suspect is that before the PHP maintainer "split up" teh 
> extensions to seperate ports each, instead of one built binary, he 
> didn't have the versioning enabled ... it was only because of the splits 
> that he added it, so it never affected us before ...
> 
> ----
> Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
> Email: scrappy@hub.org           Yahoo!: yscrappy              ICQ: 7615664