pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alex Turner <armtuk@gmail.com>
To: Mikael Carneholm <Mikael.Carneholm@wirelesscar.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: RAID stripe size question
Date: Mon, 17 Jul 2006 02:13:04 -0400
Message-ID: <33c6269f0607162313k1770ac16ld5e90e106bf5e8dc@mail.gmail.com> (raw)
In-Reply-To: <7F10D26ECFA1FB458B89C5B4B0D72C2B4E4BB1@sesrv12.wirelesscar.com>
References: <7F10D26ECFA1FB458B89C5B4B0D72C2B4E4BB1@sesrv12.wirelesscar.com>

With 18 disks dedicated to  data, you could make 100/7*9 seeks/second (7ms
av seeks time, 9 independant units) which is 128seeks/second writing on
average 64kb of data, which is 4.1MB/sec throughput worst case, probably 10x
best case so 40Mb/sec - you might want to take more disks for your data and
less for your WAL.

Someone check my math here...

And as always - run benchmarks with your app to verify

Alex.

On 7/16/06, Mikael Carneholm <Mikael.Carneholm@wirelesscar.com> wrote:
>
>  I have finally gotten my hands on the MSA1500 that we ordered some time
> ago. It has 28 x 10K 146Gb drives, currently grouped as 10 (for wal) + 18
> (for data). There's only one controller (an emulex), but I hope performance
> won't suffer too much from that. Raid level is 0+1, filesystem is ext3.
>
> Now to the interesting part: would it make sense to use different stripe
> sizes on the separate disk arrays? In theory, a smaller stripe size (8-32K)
> should increase sequential write throughput at the cost of decreased
> positioning performance, which sounds good for WAL (assuming WAL is never
> "searched" during normal operation). And for disks holding the data, a
> larger stripe size (>32K) should provide for more concurrent (small)
> reads/writes at the cost of decreased raw throughput. This is with an OLTP
> type application in mind, so I'd rather have high transaction throughput
> than high sequential read speed. The interface is a 2Gb FC so I'm throttled
> to (theoretically) 192Mb/s, anyway.
>
> So, does this make sense? Has anyone tried it and seen any performance
> gains from it?
>
> Regards,
> Mikael.
>

view thread (28+ messages)  latest in thread

Message-ID: <33c6269f0607162313k1770ac16ld5e90e106bf5e8dc@mail.gmail.com>
Permalink:  ../33c6269f0607162313k1770ac16ld5e90e106bf5e8dc@mail.gmail.com/
Also on:    postgresql.org/message-id/33c6269f0607162313k1770ac16ld5e90e106bf5e8dc@mail.gmail.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: armtuk@gmail.com, Mikael.Carneholm@wirelesscar.com
  Subject: Re: RAID stripe size question
  In-Reply-To: <33c6269f0607162313k1770ac16ld5e90e106bf5e8dc@mail.gmail.com>
  References: <7F10D26ECFA1FB458B89C5B4B0D72C2B4E4BB1@sesrv12.wirelesscar.com> <33c6269f0607162313k1770ac16ld5e90e106bf5e8dc@mail.gmail.com>

* 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