From: | Jurgen Haan <jurgen(at)easyflex(dot)nl> |
---|---|
To: | Ketema <ketema(at)gmail(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Hardware for PostgreSQL |
Date: | 2007-11-02 14:05:13 |
Message-ID: | 472B2E99.7090605@easyflex.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Ketema wrote:
> RAM? The more the merrier right? Understanding shmmax and the pg
> config file parameters for shared mem has to be adjusted to use it.
> Disks? standard Raid rules right? 1 for safety 5 for best mix of
> performance and safety?
> Any preference of SCSI over SATA? What about using a High speed (fibre
> channel) mass storage device?
You might also check out NETAPP NAS arrays.
Due to clever use of a big memory buffer and a custom filesystem on a
RAID-4 array it has performance comparable to a big RAM disk connected
through NFS.
Works quite well with OLTP (at least for us).
>
> Who has built the biggest baddest Pg server out there and what do you
> use?
>
> Thanks!
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
From | Date | Subject | |
---|---|---|---|
Next Message | Carlo Stonebanks | 2007-11-02 14:46:11 | Re: How to avoid hashjoin and mergejoin |
Previous Message | Palle Girgensohn | 2007-11-02 10:44:24 | Re: select max(field) from table much faster with a group by clause? |