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 6595C3A3AD8 for ; Sun, 31 Oct 2004 20:26:39 +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 69755-08 for ; Sun, 31 Oct 2004 20:26:20 +0000 (GMT) Received: from ngate.rdw.ru (mail.rdw.ru [195.42.172.4]) by svr1.postgresql.org (Postfix) with ESMTP id 1D1123A4270 for ; Sun, 31 Oct 2004 20:26:19 +0000 (GMT) Received: (qmail 4335 invoked by uid 50004); 31 Oct 2004 20:26:17 -0000 Received: from 192.168.0.57 by ngate.rdw.ru (envelope-from , uid 100) with qmail-scanner-1.23 ( Clear:RC:1(192.168.0.57):. Processed in 0.055348 secs); 31 Oct 2004 20:26:17 -0000 X-Qmail-Scanner-Mail-From: borz_off@cs.msu.su via ngate.rdw.ru X-Qmail-Scanner: 1.23 (Clear:RC:1(192.168.0.57):. Processed in 0.055348 secs) Received: from senoval.rdw.ru ([192.168.0.57]) (envelope-sender ) by ngate.rdw.ru (qmail-ldap-1.03) with compressed SMTP for ; 31 Oct 2004 20:26:17 -0000 Received: (qmail 18799 invoked from network); 31 Oct 2004 20:26:17 -0000 Received: from ppp01.rdw.ru (HELO [192.168.0.7]) ([192.168.0.7]) (envelope-sender ) by senoval.rdw.ru (qmail-ldap-1.03) with SMTP for ; 31 Oct 2004 20:26:16 -0000 Message-ID: <41854A72.2060608@cs.msu.su> Date: Sun, 31 Oct 2004 23:26:26 +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: "Marc G. Fournier" Cc: pgsql-www@postgresql.org Subject: Re: Inadequate hosting for www.postgresql.org? References: <4184C8EE.3080304@cs.msu.su> <20041031130007.R33702@ganymede.hub.org> In-Reply-To: <20041031130007.R33702@ganymede.hub.org> 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: 200410/332 X-Sequence-Number: 5726 Hi, Marc G. Fournier wrote: > That's why mirrors are pulled from http://www.postgresql.org, nor are > they pulled using what I'd guess you are using ( wget? ) below, but > using rsync ... hasn't been for years now ... > > In fact, over the next little while, http://www.postgresql.org will > actually be pointing to an RR DNS entry, and not even the 'base server' > ... I've just gotta sit down and update the DNS generation scripts for > this ... Uh, seems I was unclear about what I was doing. I understand of course that the site is mirrored via rsync, but consider the following: the site which resides in CVS is just a few PHP scripts, to have something to rsync you first need to *generate* the static pages. And here comes the problem: page generation is outrageously slow. In current version special scripts are used to generate static pages, but these are terrible hacks, f.e. you have to make the same change to design both in the dynamic page and the mirroring script. But they maybe run in acceptable time, I don't know, ask Dave. For the next version I just wrote a generic mirroring script behaving like wget but taking into account some specific needs (like i18n). The plus is that you don't need to change this script *at all* if you add pages or even completely redesign the site. But now it looks as if generation of full static website will take several hours. And no, this has nothing to do with network latency, the mirror generation script was run locally. Marc, page generation times of 3+ seconds are only acceptable if you do some extremely complex database queries in them, think reports. This is definitely *not* the case with the code of postgresql.org, my experience tells me that modern hardware can happily churn 5-10 of such pages *per second*. Thus: either hardware is completely inadequate or the servers are overloaded.