X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id D7794D1B9BD for ; Tue, 11 May 2004 13:55:04 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 65045-01 for ; Tue, 11 May 2004 13:54:43 -0300 (ADT) Received: from black.geophile.com (h004005242b8e.ne.client2.attbi.com [24.91.49.146]) by svr1.postgresql.org (Postfix) with ESMTP id 0D4D4D1B3CC for ; Tue, 11 May 2004 13:54:42 -0300 (ADT) Received: from black.geophile.com (localhost.localdomain [127.0.0.1]) by black.geophile.com (8.12.8/8.12.8) with ESMTP id i4BGqXxY025341; Tue, 11 May 2004 12:52:33 -0400 Received: (from apache@localhost) by black.geophile.com (8.12.8/8.12.8/Submit) id i4BGqWdQ025339; Tue, 11 May 2004 12:52:32 -0400 X-Authentication-Warning: black.geophile.com: apache set sender to jao@geophile.com using -f Received: from 64.119.142.34 ([64.119.142.34]) by geophile.com (IMP) with HTTP for ; Tue, 11 May 2004 12:52:32 -0400 Message-ID: <1084294352.40a104d04ad0d@geophile.com> Date: Tue, 11 May 2004 12:52:32 -0400 From: jao@geophile.com To: Rob Fielding Cc: Matthew Nuzum , pgsql-performance@postgresql.org Subject: Re: Configuring PostgreSQL to minimize impact of checkpoints References: <200405111335.i4BDZLDJ010593@ms-smtp-01.tampabay.rr.com> <40A0ED54.7050708@dsvr.net> In-Reply-To: <40A0ED54.7050708@dsvr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.2 X-Originating-IP: 64.119.142.34 X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.3 tagged_above=0.0 required=5.0 tests=NO_REAL_NAME X-Spam-Level: X-Archive-Number: 200405/72 X-Sequence-Number: 6903 Quoting Rob Fielding : > Assuming you're running with optimal schema and index design (ie you're > not doing extra work unnecessarily), and your backend has > better-then-default config options set-up (plenty of tips around here), > then disk arrangement is critical to smoothing the ride. The schema and queries are extremely simple. I've been experimenting with config options. One possibility I'm looking into is whether shared_buffers is too high, at 12000. We have some preliminary evidence that setting it lower (1000) reduces the demand for IO bandwidth to a point where the spikes become almost tolerable. > First tip would to take your pg_xlog and put it on another disk (and > channel). That's on my list of things to try. > Next if you're running a journalled fs, get that journal off > onto another disk (and channel). Finally, get as many disks for the data > store and spread the load across spindles. Dumb question: how do I spread the data across spindles? Do you have a pointer to something I could read? Jack Orenstein ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.