Re: how to partition disks

From: Sven Geisler <sgeisler(at)aeccom(dot)com>
To: hubert depesz lubaczewski <depesz(at)gmail(dot)com>
Cc: Pgsql-Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: how to partition disks
Date: 2006-06-14 11:41:31
Message-ID: 448FF5EB.8010808@aeccom.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Hi Hupert,

hubert depesz lubaczewski schrieb:
> On 6/14/06, *Sven Geisler* <sgeisler(at)aeccom(dot)com
> <mailto:sgeisler(at)aeccom(dot)com>> wrote:
> You should configure your discs to RAID 10 volumes.
> You should set up a separate volume for WAL.
> A volume for an additional table space may also useful.
> In your case I would do 2 partitions:
> 1. RAID 10 with 8 discs for general data
>
>
> raid 10 is of course not questionable. but are you sure that it will
> work faster than for example:
> 2 discs (raid 1) for xlog
> 6 discs (raid 10) for tables
> 6 discs (raid 10) for indices?
>

This depends on your application. Do you have a lot of disc reads?
Anyhow, I would put the xlog always to a RAID 10 volume because most of
the I/O for update and inserts is going to the xlog.

4 discs xlog
6 discs tables
4 discs tables2

This should be better. You should distribute indices on separate spindle
stacks to share the I/O. But again this depends on your application and
your server. How are the indices used? How large is your file system
cache. What does PostgreSQL effectively read from disc.

Don't forget to tune your postgresql.conf:
<http://www.powerpostgresql.com/PerfList>
<http://www.powerpostgresql.com/Downloads/terabytes_osc2005.pdf>

Cheers
Sven.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Jim C. Nasby 2006-06-14 13:57:40 Re: Confirmation of bad query plan generated by 7.4
Previous Message Böszörményi Zoltán 2006-06-14 11:30:10 Re: Precomputed constants?