Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 465C29FA4A0 for ; Thu, 19 Oct 2006 13:39:39 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 19603-04 for ; Thu, 19 Oct 2006 16:39:24 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from lynet.oppetid.no (oppetid.no [80.65.51.2]) by postgresql.org (Postfix) with ESMTP id D8B119FA12F for ; Thu, 19 Oct 2006 13:39:23 -0300 (ADT) Received: by lynet.oppetid.no (Postfix, from userid 1019) id E393111AFA9; Thu, 19 Oct 2006 18:39:22 +0200 (CEST) Date: Thu, 19 Oct 2006 18:39:22 +0200 From: Tobias Brox To: "Jim C. Nasby" Cc: Tobias Brox , pgsql-performance@postgresql.org Subject: Re: Swappiness setting on a linux pg server Message-ID: <20061019163922.GD31916@oppetid.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: Group Nordicbet User-Agent: Mutt/1.5.9i X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.135 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200610/407 X-Sequence-Number: 21536 [Jim C. Nasby - Thu at 11:31:26AM -0500] > Yeah, test setups are a good thing to have... We would need to replicate the production traffic as well to do reliable tests. Well, we'll get to that one day ... > The issue with pg_xlog is you don't need bandwidth... you need super-low > latency. The best way to accomplish that is to get a battery-backed RAID > controller that you can enable write caching on. Sounds a bit risky to me :-)