From: Jurgen Haan <jurgen@easyflex.nl>
To: Ketema <ketema@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Hardware for PostgreSQL
Date: Fri, 02 Nov 2007 15:05:13 +0100
Message-ID: <472B2E99.7090605@easyflex.nl> (raw)
In-Reply-To: <1193849108.591961.103570@22g2000hsm.googlegroups.com>
References: <1193849108.591961.103570@22g2000hsm.googlegroups.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: jurgen@easyflex.nl, ketema@gmail.com
Subject: Re: Hardware for PostgreSQL
In-Reply-To: <472B2E99.7090605@easyflex.nl>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox