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 77FBF3A4654 for ; Wed, 3 Nov 2004 20:38:15 +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 83432-07 for ; Wed, 3 Nov 2004 20:38:11 +0000 (GMT) Received: from Hueymiccailhuitl.MTU.ru (barbuda.mtu.ru [195.34.32.115]) by svr1.postgresql.org (Postfix) with ESMTP id 68FB13A464F for ; Wed, 3 Nov 2004 20:38:11 +0000 (GMT) Received: from [62.118.143.245] (ppp143-245.dialup.mtu-net.ru [62.118.143.245]) by smtp.MTU.RU (Postfix) with ESMTP id A259D17F272; Wed, 3 Nov 2004 23:38:05 +0300 (MSK) (envelope-from borz_off@cs.msu.su) Message-ID: <41894174.5020306@cs.msu.su> Date: Wed, 03 Nov 2004 23:37:08 +0300 From: Alexey Borzov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: Dave Page Cc: "Marc G. Fournier" , pgsql-www@postgresql.org Subject: Re: Inadequate hosting for www.postgresql.org References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; 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/54 X-Sequence-Number: 5785 Hi, Dave Page wrote: >>This I simply do not understand. If there is a need for >>dedicated hardware, and it is being offered, then why is it >>not being accepted? >>Didn't CommandPrompt also offer dedicated hardware? >> >>Not wanting to start another heated debate, just wanting to >>understand what the deal is - as this topic keeps getting >>regurgitated without a conclusion. > > > The problem is not the hardware from what Marc & I can tell - the > current hardware (a dual PIII with 4GB) is just ticking along with > little load, and the current website performs quite nicely. You mean, of course, "current *static* website performs quite nicely", since PHP is horribly slow there as well. I'd like to repeat, the problem is that the server is not dedicated to PostgreSQL project's needs and it has a lot of other stuff that can affect performance and is extremely hard to track: > What we seem > to have is a php performance issue that we haven't tracked down yet > which only noticably affects the beta site.