pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: William Yu <wyu@talisys.com>
To: pgsql-performance@postgresql.org
Subject: Re: Hardware recommendations to scale to silly load
Date: Fri, 29 Aug 2003 00:05:03 -0700
Message-ID: <bimtv0$o0l$1@news.hub.org> (raw)
In-Reply-To: <3F4E5DA9.6396.5C8916@localhost>
References: <1061953146.18108.291.camel@haggis>
	<3F4E5DA9.6396.5C8916@localhost>

Shridhar Daithankar wrote:
>> Be careful here, we've seen that with the P4 Xeon's that are
>>hyper-threaded and a system that has very high disk I/O causes the
>>system to be sluggish and slow. But after disabling the hyper-threading
>>itself, our system flew..
> 
> Anybody has opteron working? Hows' the performance?

Yes. I'm using an 2x 1.8GHz Opteron system w/ 8GB of RAM. Right now, I'm 
still using 32-bit Linux -- I'm letting others be the 64-bit guinea 
pigs. :) I probably will get a cheapie 1x Opteron machine first and test 
the 64-bit kernel/libraries thoroughly before rolling it out to production.

As for performance, the scaling is magnificient -- even when just using 
PAE instead of 64-bit addressing. At low transaction counts, it's only 
~75% faster than the 2x Athlon 1800+ MP it replaced. But once the 
transactions start coming in, the gap is as high as 5x. My w-a-g: since 
each CPU has an integrated memory controller, you avoid memory bus 
contention which is probably the major bottleneck as transaction load 
increases. (I've seen Opteron several vs Xeon comparisons where 
single-connection tests are par for both CPUs but heavy-load tests favor 
the Opteron by a wide margin.) I suspect the 4X comparisons would tilt 
even more towards AMD's favor.

We should see a boost when we move to 64-bit Linux and hopefully another 
one when NUMA for Linux is production-stable.




view thread (45+ messages)  latest in thread

Message-ID: <bimtv0$o0l$1@news.hub.org>
Permalink:  ../bimtv0$o0l$1@news.hub.org/
Also on:    postgresql.org/message-id/bimtv0$o0l$1@news.hub.org

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: wyu@talisys.com
  Subject: Re: Hardware recommendations to scale to silly load
  In-Reply-To: <bimtv0$o0l$1@news.hub.org>
  References: <1061953146.18108.291.camel@haggis> <3F4E5DA9.6396.5C8916@localhost> <bimtv0$o0l$1@news.hub.org>

* 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