From: | "David Rees" <drees76(at)gmail(dot)com> |
---|---|
To: | "Peter Schuller" <peter(dot)schuller(at)infidyne(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Occasional Slow Commit |
Date: | 2008-11-06 15:47:27 |
Message-ID: | 72dbd3150811060747u7f3c2aadv3c6658d285d74455@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, Nov 6, 2008 at 2:21 AM, Peter Schuller
<peter(dot)schuller(at)infidyne(dot)com> wrote:
>> I also found that my write cache was set to WriteThrough instead of
>> WriteBack, defeating the purpose of having a BBU and that my secondary
>> server apparently doesn't have a BBU on it. :-(
>
> Note also that several RAID controllers will periodically drop the
> write-back mode during battery capacity tests. If you care about
> consistently/deterministically having full performance (with
> white-backed battery protected caching), you probably want to confirm
> your controller behavior here.
>
> (I've seen this on at least LSI based controllers in Dell 2950:s, and
> also on some 3wares.)
I can confirm that this is the case by reviewing the logs stored on
the MegaRAID controller that have a BBU and had WriteBack configured.
The controller also lets you know (using the MegaCli utility) what
setting is configured, and what setting is in effect.
In the case of the machines without a BBU on them, they are configured
to be in WriteBack, but are actually running in WriteThrough.
-Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2008-11-06 16:07:06 | Re: Occasional Slow Commit |
Previous Message | Helio Campos Mello de Andrade | 2008-11-06 12:26:20 | Re: PostgreSQL OR performance |