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 27E01D1B1CF for ; Thu, 5 Aug 2004 03:40:48 -0300 (ADT) 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 30737-07 for ; Thu, 5 Aug 2004 06:40:42 +0000 (GMT) Received: from boutiquenumerique.com (gailleton-2-82-67-9-10.fbx.proxad.net [82.67.9.10]) by svr1.postgresql.org (Postfix) with ESMTP id ADEC5D1B1A1 for ; Thu, 5 Aug 2004 03:40:34 -0300 (ADT) Received: (qmail 10793 invoked from network); 5 Aug 2004 08:40:33 +0200 Received: from unknown (HELO musicbox) (192.168.0.2) by gailleton-2-82-67-9-10.fbx.proxad.net with SMTP; 5 Aug 2004 08:40:33 +0200 To: "PostgreSQL Performance" Subject: Re: Performance Bottleneck References: <410FDC53.5080509@bigfoot.com> <20040804153624.GA27551@pobox.com> <41110D06.5090900@ethereal-realms.org> Message-ID: Date: Thu, 05 Aug 2004 08:40:35 +0200 From: =?iso-8859-15?Q?Pierre-Fr=E9d=E9ric_Caillaud?= Organization: =?iso-8859-15?Q?La_Boutique_Num=E9rique?= Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: <41110D06.5090900@ethereal-realms.org> User-Agent: Opera M2/7.50 (Linux, build 673) 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: 200408/60 X-Sequence-Number: 7696 Apache processes running for 30 minutes ?..... My advice : use frames and Javascript ! In your webpage, you have two frames : "content" and "refresh". "content" starts empty (say, just a title on top of the page). "refresh" is refreshed every five seconds from a script on your server. This script generates a javascript which "document.write()'s" new entries in the "content" frame, thus adding new records in the upper frame. Thus, the refreshing uses a new request every 5 seconds, which terminates very fast, and does not hog an Apache process. Turn keepalive timeout down.