From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Kari Lavikka <tuner(at)bdb(dot)fi> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Finding bottleneck |
Date: | 2005-08-08 19:27:25 |
Message-ID: | 8434.1123529245@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Kari Lavikka <tuner(at)bdb(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-08-09 00:58:26 | Re: Why hash join instead of nested loop? |
Previous Message | Kari Lavikka | 2005-08-08 17:54:38 | Re: Finding bottleneck |