pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gavin Hamill <gdh@laterooms.com>
To: pgsql-performance@postgresql.org
Subject: Re: pg 8.1.3, AIX, huge box, painfully slow.
Date: Fri, 7 Apr 2006 22:24:43 +0100
Message-ID: <20060407222443.97ddf152.gdh@laterooms.com> (raw)
In-Reply-To: <1144441457.32269.29.camel@state.g2switchworks.com>
References: <20060407185823.abe93017.gdh@laterooms.com>
	<1144436060.32269.13.camel@state.g2switchworks.com>
	<20060407205919.a091da26.gdh@laterooms.com>
	<1144441457.32269.29.camel@state.g2switchworks.com>

On Fri, 07 Apr 2006 15:24:18 -0500
Scott Marlowe <smarlowe@g2switchworks.com> wrote:

> > See reply to Tom Lane :)
> 
> I didn't see one go by yet...  Could be sitting in the queue.

If it's not arrived by now - EXPLAIN ANALYZE doesn't tell me
anything :)

> Let us know if changing the fsync setting helps.  Hopefully that's all
> the problem is.

fsync's already off - yes a bit scary, but our I/O is only about
500KB/sec writing.. the whole db fits in RAM / kernel disk cache, and
I'd rather have performance than security at this exact moment..
 
> Off on a tangent.  If the aggregate memory bandwidth of the pSeries is
> no greater than you Xeon you might not see a big improvement if you
> were memory bound before.  If you were CPU bound, you may or may not
> see an improvement.

I did look into the specs of the system, and the memory bw on the
pSeries was /much/ greater than the Xeon - it's one of the things that
really pushed me towards it in the end. I forget the figures, but it
was 3 or 4 times greater.

> Can you describe the disc subsystems in the two machines for us?  What
> kind of read / write load you have?  It could be the older box was
> running on IDE drives with fake fsync responses which would lie, be
> fast, but not reliable in case of a power outage.

Again, I'm confident that I/O's not the killer here.. the Xeon is a Dell
6850- hardware RAID1.. SCSI drives.

> > Multi-Opteron was the other thing we considered but decided to give
> > 'Big Iron' UNIX a whirl...
> 
> It still might be a good choice, if it's a simple misconfiguration
> issue.
> 
> But man, those new multiple core opterons can make some impressive
> machines for very little money.

So I see - we could buy two quad-opterons for the cost of renting this
pSeries for a month....

Cheers,
Gavin.



view thread (30+ messages)  latest in thread

Message-ID: <20060407222443.97ddf152.gdh@laterooms.com>
Permalink:  ../20060407222443.97ddf152.gdh@laterooms.com/
Also on:    postgresql.org/message-id/20060407222443.97ddf152.gdh@laterooms.com

 · 

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: gdh@laterooms.com
  Subject: Re: pg 8.1.3, AIX, huge box, painfully slow.
  In-Reply-To: <20060407222443.97ddf152.gdh@laterooms.com>

* 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