pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Jim C. Nasby <jnasby@pervasive.com>
Cc: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: mark@mark.mielke.cc, Bill Moran <wmoran@collaborativefusion.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Large (8M) cache vs. dual-core CPUs
Date: Wed, 26 Apr 2006 18:16:46 -0400 (EDT)
Message-ID: <200604262216.k3QMGkk15952@candle.pha.pa.us> (raw)
In-Reply-To: <20060426220929.GY97354@pervasive.com>

Jim C. Nasby wrote:
> On Wed, Apr 26, 2006 at 10:27:18AM -0500, Scott Marlowe wrote:
> > If you haven't actually run a heavy benchmark of postgresql on the two
> > architectures, please don't make your decision based on other
> > benchmarks.  Since you've got both a D920 and an X2 3800, that'd be a
> > great place to start.  Mock up some benchmark with a couple dozen
> > threads hitting the server at once and see if the Intel can keep up.  It
> 
> Or better yet, use dbt* or even pgbench so others can reproduce...

For why Opterons are superior to Intel for PostgreSQL, see:

	http://techreport.com/reviews/2005q2/opteron-x75/index.x?pg=2

Section "MESI-MESI-MOESI Banana-fana...".  Specifically, this part about
the Intel implementation:

	The processor with the Invalid data in its cache (CPU 0, let's say)
	might then wish to modify that chunk of data, but it could not do so
	while the only valid copy of the data is in the cache of the other
	processor (CPU 1). Instead, CPU 0 would have to wait until CPU 1 wrote
	the modified data back to main memory before proceeding.and that takes
	time, bus bandwidth, and memory bandwidth. This is the great drawback of
	MESI.

AMD transfers the dirty cache line directly from cpu to cpu.  I can
imaging that helping our test-and-set shared memory usage quite a bit.

-- 
  Bruce Momjian   http://candle.pha.pa.us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +



view thread (40+ messages)  latest in thread

Message-ID: <200604262216.k3QMGkk15952@candle.pha.pa.us>
Permalink:  ../200604262216.k3QMGkk15952@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200604262216.k3QMGkk15952@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, jnasby@pervasive.com, smarlowe@g2switchworks.com, wmoran@collaborativefusion.com
  Subject: Re: Large (8M) cache vs. dual-core CPUs
  In-Reply-To: <200604262216.k3QMGkk15952@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