From: Robert Treat <xzilla@users.sourceforge.net>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Tuning scenarios (was Changing the default
Date: 20 Feb 2003 18:35:44 -0500
Message-ID: <1045784144.15881.92.camel@camel> (raw)
In-Reply-To: <200302201433.02654.josh@agliodbs.com>
References: <303E00EBDD07B943924382E153890E5434A909@cuthbert.rcsinc.local>
<200302140936.02011.josh@agliodbs.com>
<1045778701.14518.81.camel@camel>
<200302201433.02654.josh@agliodbs.com>
On Thu, 2003-02-20 at 17:33, Josh Berkus wrote:
>
> Robert,
>
> > > 1) Location of the pg_xlog for heavy-update databases.
> >
> > I see you put this up pretty high on the list. Do you feel this is the
> > most important thing you can do? For example, if you had a two drive
> > installation, would you load the OS and main database files on 1 disk
> > and put the pg_xlog on the second disk above all other configurations?
>
> Yes, actually. On machines with 2 IDE disks, I've found that this can make
> as much as 30% difference in speed of serial/large UPDATE statements.
Do you know how well those numbers hold up under scsi and/ or raid based
system? (I'd assume anyone doing serious work would run scsi)
>
> > Ideally I recommend 3 disks, one for os, one for data, one for xlog; but
> > if you only had 2 would the added speed benefits be worth the additional
> > recovery complexity (if you data/xlog are on the same disk, you have 1
> > point of failure, one disk for backing up)
>
> On the other hand, with the xlog on a seperate disk, the xlog and the database
> disks are unlikely to fail at the same time. So I don't personally see it as
> a recovery problem, but a benefit.
>
ok (playing a bit of devil's advocate here), but you have two possible
points of failure, the data disk and the xlog disk. If either one goes,
your in trouble. OTOH if you put the OS disk on one drive and it goes,
your database and xlog are still safe on the other drive.
Robert Treat
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: xzilla@users.sourceforge.net, josh@agliodbs.com
Subject: Re: Tuning scenarios (was Changing the default
In-Reply-To: <1045784144.15881.92.camel@camel>
References: <303E00EBDD07B943924382E153890E5434A909@cuthbert.rcsinc.local> <200302140936.02011.josh@agliodbs.com> <1045778701.14518.81.camel@camel> <200302201433.02654.josh@agliodbs.com> <1045784144.15881.92.camel@camel>
* 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