From: | Karl Denninger <karl(at)denninger(dot)net> |
---|---|
To: | Robert Powell <bob(at)hotchkiss(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Redundant file server for postgres |
Date: | 2008-03-16 18:29:15 |
Message-ID: | 47DD66FB.3010000@denninger.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
What's the expected transaction split (read/write)?
If mostly READs (e.g. SELECTs) then its very, very hard to do better
from a performance perspective than Raid 1 with the transaction log on a
separate array (physically separate spindles)
I run a VERY busy web forum on a Quadcore Intel box with this setup and
it is very fast. Really quite amazing when you get right down to it.
The latest release of the PostgreSQL code markedly improved query
optimization, by the way. The performance improvement when I migrated
over was quite stunning.
Karl Denninger (karl(at)denninger(dot)net)
http://www.denninger.net
Robert Powell wrote:
>
> To whom it may concern,
>
>
>
> I'm looking for a file server that will give me a high level of
> redundancy and high performance for a postgres database. The server
> will be running only postgres as a backend service, connected to a
> front end server with the application on it.
>
> I was thinking along the lines of a RAID 10 setup with a very fast
> processor.
>
>
>
> Any suggestions would be greatly appreciated.
>
>
>
> Bob Powell
>
> The Hotchkiss School
>
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2008-03-16 18:33:35 | Re: Redundant file server for postgres |
Previous Message | Robert Powell | 2008-03-16 17:55:36 | Redundant file server for postgres |