pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Hannes Dorbath <light@theendofthetunnel.de>
To: Scott Marlowe <scott.marlowe@gmail.com>
Subject: Re: Performance on 8CPU's and 32GB of RAM
Date: Wed, 05 Sep 2007 10:20:31 +0200
Message-ID: <46DE66CF.9000903@theendofthetunnel.de> (raw)
In-Reply-To: <dcc563d10709041615s305ae98bm92dee61ab199b7c4@mail.gmail.com>
References: <fbkn5d$cfq$1@news.hub.org>
	<20070904230639.GA23731@alvh.no-ip.org>
	<dcc563d10709041615s305ae98bm92dee61ab199b7c4@mail.gmail.com>

On 05.09.2007 01:15, Scott Marlowe wrote:
> On 9/4/07, Alvaro Herrera <alvherre@commandprompt.com> wrote:
>> Carlo Stonebanks wrote:
>>> A client is moving their postgresql db to a brand new Windows 2003 x64
>>> server with 2 quad cores and 32GB of RAM. It is a dedicated server to run
>>> 8.2.4.
>> Large shared_buffers and Windows do not mix.  Perhaps you should leave
>> the shmem config low, so that the kernel can cache the file pages.
> 
> But yeah, the I/O, that's the big one.  If it's just a single or a
> couple of IDE drives, it's not gonna be able to handle much load.

Right, additionally NTFS is really nothing to use on any serious disc array.


-- 
Regards,
Hannes Dorbath



view thread (35+ messages)  latest in thread

Message-ID: <46DE66CF.9000903@theendofthetunnel.de>
Permalink:  ../46DE66CF.9000903@theendofthetunnel.de/
Also on:    postgresql.org/message-id/46DE66CF.9000903@theendofthetunnel.de

 · 

reply

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: light@theendofthetunnel.de, scott.marlowe@gmail.com
  Subject: Re: Performance on 8CPU's and 32GB of RAM
  In-Reply-To: <46DE66CF.9000903@theendofthetunnel.de>

* 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