pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Paul Tuckfield <paul@tuckfield.com>
Cc: pgsql-performance@postgresql.org
Cc: shannyconsulting@earthlink.net
Subject: Re: Has anyone run on the new G5 yet
Date: Sat, 6 Dec 2003 08:19:21 -0500 (EST)
Message-ID: <200312061319.hB6DJL916645@candle.pha.pa.us> (raw)
In-Reply-To: <1070526289.4666.35.camel@localhost.localdomain>

Paul Tuckfield wrote:
> Biggest problem I've had in the past w. linux in general is that it
> seems to make poor VM choices under heavy filesystem IO.  I don't really
> get exactly where it's going wrong , but I've had numerous experiences
> on older systems where bursty IO would seem to cause paging on the box
> (pageout of pieces of the oracle SGA shared memory) which is a
> performance disaseter.  It seems to happen even when the shared memory
> was sized reasonably below the size of physical ram, presumably because
> linux is too aggressive in allocating filesystem cache (?) anyway, it
> seems to make decisions based on desire for zippy workstation
> performance and gets burned on thruput on database servers.  I'm
> guessing this may be an issue for you , when doing heavy IO.  Thing is,
> it'll show like you're IO bound kindof because you're thrashing.

This is not surprising.  There has always been an issue with dynamic
buffer cache systems contending with memory used by processes.  It takes
a long time to get the balance right, and still there might be cases
where it gets things wrong.  Isn't there a Linux option to lock shared
memory in to RAM?   If so, we should document this in our manuals, but
right now, there is no mention of it.
  
-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073



view thread (9+ messages)

Message-ID: <200312061319.hB6DJL916645@candle.pha.pa.us>
Permalink:  ../200312061319.hB6DJL916645@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200312061319.hB6DJL916645@candle.pha.pa.us

 · 

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: pgman@candle.pha.pa.us, paul@tuckfield.com, shannyconsulting@earthlink.net
  Subject: Re: Has anyone run on the new G5 yet
  In-Reply-To: <200312061319.hB6DJL916645@candle.pha.pa.us>

* 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