From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Vivek Khera <khera(at)kcilink(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: optimum postgres server configuration |
Date: | 2003-07-24 20:36:17 |
Message-ID: | 200307242036.h6OKaHb26476@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Vivek Khera wrote:
> >>>>> "td" == tom dyson <tom(at)torchbox(dot)com> writes:
>
> td> and software, given a smallish fixed budget (around $US 2000)? In
> td> particular, should we prioritise
>
> td> * Disk speed
> td> * Hardware RAID
> td> * Memory
> td> * Processor speed
> td> * Processor type
> td> * Multiple processors
>
> Like others have said, splurge on the disk speed. Personally I use
> hardware RAID 10, but I'm not on a tight budget. Any modern system
> will have enough CPU power. Next thing to maximize is RAM.
Alot of RAID system have sophisticated battery-backed cache, that helps
PostgreSQL a lot. The RAID controller centralizes all that cache,
rather than trying to get individual disk drives with that capability.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Clay Luther | 2003-07-24 20:43:11 | Re: Postgres unique index checking and atomic transactions |
Previous Message | Sanjay Manandhar | 2003-07-24 20:32:14 | COPY command |