From: | John Lister <john(dot)lister(at)kickstone(dot)co(dot)uk> |
---|---|
To: | Jan Nielsen <jan(dot)sture(dot)nielsen(at)gmail(dot)com> |
Cc: | sthomas(at)peak6(dot)com, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Configuration Recommendations |
Date: | 2012-05-03 06:54:10 |
Message-ID: | 4FA22B92.6050103@kickstone.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 03/05/2012 03:10, Jan Nielsen wrote:
>
> 300GB RAID10 2x15k drive for OS on local storage
> */dev/sda1 RA* 4096
> */dev/sda1 FS* ext4
> */dev/sda1 MO*
>
> 600GB RAID 10 8x15k drive for $PGDATA on SAN
> *IO Scheduler sda* noop anticipatory deadline [cfq]
> */dev/sdb1 RA* 4096
> */dev/sdb1 FS* xfs
> */dev/sdb1 MO* allocsize=256m,attr2,logbufs=8,logbsize=256k,noatime
>
> 300GB RAID 10 2x15k drive for $PGDATA/pg_xlog on SAN
> *IO Scheduler sdb* noop anticipatory deadline [cfq]
> */dev/sde1 RA* 4096
> */dev/sde1 FS* xfs
> */dev/sde1 MO* allocsize=256m,attr2,logbufs=8,logbsize=256k,noatime
> *
I was wondering if it would be better to put the xlog on the same disk
as the OS? Apart from the occasional log writes I'd have thought most OS
data is loaded into cache at the beginning, so you effectively have an
unused disk. This gives you another spindle (mirrored) for your data.
Or have I missed something fundamental?
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2012-05-03 07:26:40 | Re: Several optimization options (config/hardware) |
Previous Message | Jan Nielsen | 2012-05-03 02:10:03 | Re: Configuration Recommendations |