X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id F387F3A48DB for ; Thu, 4 Nov 2004 18:20:45 +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 66734-07 for ; Thu, 4 Nov 2004 18:20:36 +0000 (GMT) Received: from neptune.lgu.ac.uk (neptune.lgu.ac.uk [140.97.30.6]) by svr1.postgresql.org (Postfix) with ESMTP id 5C7243A48EC for ; Thu, 4 Nov 2004 18:20:35 +0000 (GMT) Received: from solent (cal42-234.lgu.ac.uk [140.97.42.234]) by neptune.lgu.ac.uk (8.12.10/8.12.10) with ESMTP id iA4IK5O6027673; Thu, 4 Nov 2004 18:20:05 GMT Reply-To: From: "Matt Clark" To: "'Martin Foster'" Cc: "'Matthew Nuzum'" , "'PostgreSQL Performance'" Subject: Re: Restricting Postgres Date: Thu, 4 Nov 2004 18:20:18 -0000 Organization: Ymogen Ltd Message-ID: <003301c4c29a$f052d910$8300a8c0@solent> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <418A6DFD.8010803@ethereal-realms.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal X-LGU-MailScanner: Found to be clean X-MailScanner-From: matt@ymogen.net 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/52 X-Sequence-Number: 9006 > Correct the 75% of all hits are on a script that can take=20 > anywhere from=20 > a few seconds to a half an hour to complete. The script=20 > essentially=20 > auto-flushes to the browser so they get new information as it arrives=20 > creating the illusion of on demand generation. This is more like a streaming data server, which is a very different = beast from a webserver, and probably better suited to the job. Usually either multithreaded or single-process using select() (just like Squid). You = could probably build one pretty easily. Using a 30MB Apache process to serve = one client for half an hour seems like a hell of a waste of RAM. > A squid proxy would probably cause severe problems when=20 > dealing with a=20 > script that does not complete output for a variable rate of time. No, it's fine, squid gives it to the client as it gets it, but can = receive from the server faster.