Re: moving pg_xlog -- yeah, it's worth it!

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Jesper Krogh" <jesper(at)krogh(dot)cc>, "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: moving pg_xlog -- yeah, it's worth it!
Date: 2010-02-11 17:48:37
Message-ID: 4B73EE95020000250002F1CC@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Jesper Krogh <jesper(at)krogh(dot)cc> wrote:
>
>> Sorry if it is obvious.. but what filesystem/OS are you using and
>> do you have BBU-writeback on the main data catalog also?

> File system is xfs noatime,nobarrier for all data; OS is on ext3.
> I *think* the pg_xlog mirrored pair is hanging off the same
> BBU-writeback controller as the big RAID, but I'd have to track
> down the hardware tech to confirm

Another example of why I shouldn't trust my memory. Per the
hardware tech:


OS: /dev/sda is RAID1 - 2 x 2.5" 15k SAS disk
pg_xlog: /dev/sdb is RAID1 - 2 x 2.5" 15k SAS disk

These reside on a ServeRAID-MR10k controller with 256MB BB cache.


data: /dev/sdc is RAID5 - 30 x 3.5" 15k SAS disk

These reside on the DS3200 disk subsystem with 512MB BB cache per
controller and redundant drive loops.


At least I had the file systems and options right. ;-)

-Kevin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Alvaro Herrera 2010-02-11 17:57:52 Re: moving pg_xlog -- yeah, it's worth it!
Previous Message Scott Marlowe 2010-02-11 17:42:04 Re: Dell PERC H700/H800