pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kari Lavikka <tuner@bdb.fi>
Cc: pgsql-performance@postgresql.org
Subject: Re: Finding bottleneck
Date: Mon, 08 Aug 2005 15:27:25 -0400
Message-ID: <8434.1123529245@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.HPX.4.62.0508082020421.3361@purple.bdb.fi>
References: <6EE64EF3AB31D5448D0007DD34EEB3417DD026@Herge.rcsinc.local>
	<Pine.HPX.4.62.0508081839420.3361@purple.bdb.fi>
	<29384.1123520200@sss.pgh.pa.us>
	<Pine.HPX.4.62.0508082020421.3361@purple.bdb.fi>

Kari Lavikka <tuner@bdb.fi> writes:
> Disk configurations looks something like this:
>    sda: data (10 spindles, raid10)
>    sdb: xlog & clog (2 spindles, raid1)
>    sdc: os and other stuff

That's definitely wrong.  Put clog on the data disk.  The entire point
of giving xlog its own spindle is that you don't ever want the disk
heads moving off the current xlog file.  I'm not sure how much this is
hurting you, given that clog is relatively low volume, but if you're
going to go to the trouble of putting xlog on a separate spindle then
it should be a completely dedicated spindle.

			regards, tom lane



view thread (22+ messages)  latest in thread

Message-ID: <8434.1123529245@sss.pgh.pa.us>
Permalink:  ../8434.1123529245@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/8434.1123529245@sss.pgh.pa.us

 · 

reply
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: tgl@sss.pgh.pa.us, tuner@bdb.fi
  Subject: Re: Finding bottleneck
  In-Reply-To: <8434.1123529245@sss.pgh.pa.us>

* 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