From: jao@geophile.com
To: Rob Fielding <rob@dsvr.net>
Cc: Matthew Nuzum <cobalt@bearfruit.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Configuring PostgreSQL to minimize impact of checkpoints
Date: Tue, 11 May 2004 12:52:32 -0400
Message-ID: <1084294352.40a104d04ad0d@geophile.com> (raw)
In-Reply-To: <40A0ED54.7050708@dsvr.net>
References: <200405111335.i4BDZLDJ010593@ms-smtp-01.tampabay.rr.com>
<40A0ED54.7050708@dsvr.net>
Quoting Rob Fielding <rob@dsvr.net>:
> 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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: jao@geophile.com, rob@dsvr.net, cobalt@bearfruit.org
Subject: Re: Configuring PostgreSQL to minimize impact of checkpoints
In-Reply-To: <1084294352.40a104d04ad0d@geophile.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox