From: William Yu <wyu@talisys.com>
To: pgsql-performance@postgresql.org
Subject: Re: Large (8M) cache vs. dual-core CPUs
Date: Wed, 26 Apr 2006 08:24:35 -0700
Message-ID: <e2o3bk$1v7h$1@news.hub.org> (raw)
In-Reply-To: <444F870D.2000307@boreham.org>
References: <20060425141435.6c8c163c.wmoran@collaborativefusion.com>
<1145990018.23538.234.camel@state.g2switchworks.com>
<20060425183817.GA9241@mark.mielke.cc>
<1145990551.23538.244.camel@state.g2switchworks.com>
<20060426005440.GA12711@mark.mielke.cc>
<20060426011701.GB12711@mark.mielke.cc>
<e2nvhj$1h3b$1@news.hub.org>
<444F870D.2000307@boreham.org>
David Boreham wrote:
> It isn't only Postgres. I work on a number of other server applications
> that also run much faster on Opterons than the published benchmark
> figures would suggest they should. They're all compiled with gcc4,
> so possibly there's a compiler issue. I don't run Windows on any
> of our Opteron boxes so I can't easily compare using the MS compiler.
Maybe it's just a fact that the majority of x86 64-bit development for
open source software happens on Opteron/A64 machines. 64-bit AMD
machines were selling a good year before 64-bit Intel machines were
available. And even after Intel EMT64 were available, anybody in their
right mind would have picked AMD machines over Intel due to
cost/heat/performance. So you end up with 64-bit OSS being
developed/optimized for Opterons and the 10% running Intel EMT64 handle
compatibility issues.
Would be interesting to see a survey of what machines OSS developers use
to write/test/optimize their code.
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: wyu@talisys.com
Subject: Re: Large (8M) cache vs. dual-core CPUs
In-Reply-To: <e2o3bk$1v7h$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