From: | "Steve Poe" <steve(dot)poe(at)gmail(dot)com> |
---|---|
To: | "Scott Marlowe" <smarlowe(at)g2switchworks(dot)com> |
Cc: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, "Luke Lonergan" <LLonergan(at)greenplum(dot)com>, "Alex Turner" <armtuk(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Postgresql Performance on an HP DL385 and |
Date: | 2006-08-09 23:47:10 |
Message-ID: | 721b21dc0608091647w7116e1b6xf1313d4d1df34a4d@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
I believe it does, I'll need to check.Thanks for the correction.
Steve
On 8/9/06, Scott Marlowe <smarlowe(at)g2switchworks(dot)com> wrote:
>
> On Wed, 2006-08-09 at 16:11, Steve Poe wrote:
> > Jim,
> >
> > I'll give it a try. However, I did not see anywhere in the BIOS
> > configuration of the 642 RAID adapter to enable writeback. It may have
> > been mislabled cache accelerator where you can give a percentage to
> > read/write. That aspect did not change the performance like the LSI
> > MegaRAID adapter does.
>
> Nope, that's not the same thing.
>
> Does your raid controller have batter backed cache, or plain or regular
> cache? write back is unsafe without battery backup.
>
> The default is write through (i.e. the card waits for the data to get
> written out before acking an fsync). In write back, the card's driver
> writes the data to the bb cache, then returns on an fsync while the
> cache gets written out at leisure. In the event of a loss of power, the
> cache is flushed on restart.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Poe | 2006-08-10 01:24:07 | Re: Postgresql Performance on an HP DL385 and |
Previous Message | Tom Lane | 2006-08-09 22:37:00 | Re: shared_buffer optimization |