From: Craig Ringer <craig@postnewspapers.com.au>
To: Dave Crooke <dcrooke@gmail.com>
Cc: Carlo Stonebanks <stonec.register@sympatico.ca>
Cc: pgsql-performance@postgresql.org
Subject: Re: New server to improve performance on our large and busy DB - advice? (v2)
Date: Fri, 15 Jan 2010 08:46:09 +0800
Message-ID: <4B4FBAD1.4040304@postnewspapers.com.au> (raw)
In-Reply-To: <ca24673e1001141435w19fd4930o2caea62087a4af50@mail.gmail.com>
References: <hio221$5hv$1@news.hub.org>
<ca24673e1001141435w19fd4930o2caea62087a4af50@mail.gmail.com>
On 15/01/2010 6:35 AM, Dave Crooke wrote:
> I'll bite ....
>
>
> 1. In general, RAID-10 is the only suitable RAID configuration for a
> database. The decision making comes in how many drives, and splitting
> stuff up into LUNs (like putting pg_xlog on its own LUN).
>
>
> The biggest problem with Postgres on Windows is that it only comes in
> 32-bit. RAM is the ultimate performance tweak for an RDBMS, and to make
> proper use of modern amounts of RAM, you need a 64-bit executable.
.... though that's much less important for Pg than for most other
things, as Pg uses a one-process-per-connection model and lets the OS
handle much of the caching. So long as the OS can use all that RAM for
caching, Pg will benefit, and it's unlikely you need >2GB for any given
client connection or for the postmaster.
It's nice to have the flexibility to push up shared_buffers, and it'd be
good to avoid any overheads in running 32-bit code on win64. However,
it's not that unreasonable to run a 32-bit Pg on a 64-bit OS and expect
good performance.
You can always go 64-bit once 8.5/9.0 hits and has stabilized, anyway.
--
Craig Ringer
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: craig@postnewspapers.com.au, dcrooke@gmail.com, stonec.register@sympatico.ca
Subject: Re: New server to improve performance on our large and busy DB - advice? (v2)
In-Reply-To: <4B4FBAD1.4040304@postnewspapers.com.au>
* 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