From: | Decibel! <decibel(at)decibel(dot)org> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | postgresql performance list <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: asynchronous commit feature |
Date: | 2007-08-27 20:11:38 |
Message-ID: | 20070827201138.GM54309@nasby.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, Aug 23, 2007 at 09:09:00AM -0400, Merlin Moncure wrote:
> I'm testing the new asynch commit feature on various raid
> configurations and my early findings is that it reduces the impact of
> keeping wal and data on the same volume. I have 10 disks to play
> with, and am finding that it's faster to do a 10 drive raid 10 rather
> than 8 drive raid 10 + two drive wal.
>
> anybody curious about the results, feel free to drop a line. I think
> this will be a popular feature.
With or without a write cache on the RAID controller? I suspect that for
many systems, a write-caching controller will be very similar in
performance to async commit.
--
Decibel!, aka Jim Nasby decibel(at)decibel(dot)org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Decibel! | 2007-08-27 21:00:41 | Re: significant vacuum issues - looking for suggestions |
Previous Message | Tom Lane | 2007-08-27 15:55:46 | Re: Performance issue |