From: Markus Schaber <schabi@logix-tt.com>
To: pgsql-performance@postgresql.org
Cc: Mikael Carneholm <Mikael.Carneholm@WirelessCar.com>
Subject: Re: RAID stripe size question
Date: Mon, 17 Jul 2006 11:47:05 +0200
Message-ID: <44BB5C99.5070205@logix-tt.com> (raw)
In-Reply-To: <7F10D26ECFA1FB458B89C5B4B0D72C2B4E4BC3@sesrv12.wirelesscar.com>
References: <7F10D26ECFA1FB458B89C5B4B0D72C2B4E4BC3@sesrv12.wirelesscar.com>
Hi, Mikael,
Mikael Carneholm wrote:
> An 0+1 array of 4 disks *could* be enough, but I'm still unsure how WAL
> activity correlates to "normal data" activity (is it 1:1, 1:2, 1:4,
> ...?)
I think the main difference is that the WAL activity is mostly linear,
where the normal data activity is rather random access. Thus, a mirror
of few disks (or, with good controller hardware, raid6 on 4 disks or so)
for WAL should be enough to cope with a large set of data and index
disks, who have a lot more time spent in seeking.
Btw, it may make sense to spread different tables or tables and indices
onto different Raid-Sets, as you seem to have enough spindles.
And look into the commit_delay/commit_siblings settings, they allow you
to deal latency for throughput (means a little more latency per
transaction, but much more transactions per second throughput for the
whole system.)
HTH,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: schabi@logix-tt.com, Mikael.Carneholm@WirelessCar.com
Subject: Re: RAID stripe size question
In-Reply-To: <44BB5C99.5070205@logix-tt.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