| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com>, alex(at)neteconomist(dot)com, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: which dual-CPU hardware/OS is fastest for PostgreSQL? |
| Date: | 2005-03-28 20:57:08 |
| Message-ID: | 1112043428.26232.43.camel@jd2.commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> I assume AMCC == 3ware now?
>
> Has anyone verified that fsync is safe on these controllers? Ie, that they
> aren't caching writes and "lying" about the write completing like IDE
> drives often do by default?
The higher end AMCC/3ware controllers actually warn you about using
write-cache. You have to explicitly turn it on within the controller
bios.
They also have optional battery backed cache.
Sincerely,
Joshua D. Drake
>
--
Command Prompt, Inc., Your PostgreSQL solutions company. 503-667-4564
Custom programming, 24x7 support, managed services, and hosting
Open Source Authors: plPHP, pgManage, Co-Authors: plPerlNG
Reliable replication, Mammoth Replicator - http://www.commandprompt.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2005-03-28 21:05:59 | Re: Preventing query from hogging server |
| Previous Message | Greg Stark | 2005-03-28 20:09:29 | Re: which dual-CPU hardware/OS is fastest for PostgreSQL? |