| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Steve Poe <steve(dot)poe(at)gmail(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 21:37:28 |
| Message-ID: | 1155159448.20252.121.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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 | Scott Marlowe | 2006-08-09 21:50:30 | Re: most bang for buck with ~ $20,000 |
| Previous Message | Jim C. Nasby | 2006-08-09 21:35:43 | Re: most bang for buck with ~ $20,000 |