From: Josh Berkus <josh@agliodbs.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: William Yu <wyu@talisys.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Help specifying new machine
Date: Thu, 19 Aug 2004 09:18:31 -0700
Message-ID: <200408190918.31797.josh@agliodbs.com> (raw)
In-Reply-To: <12077.1092894555@sss.pgh.pa.us>
References: <20040809165657.GB15169@campbell-lange.net>
<cg1a6d$2aml$1@news.hub.org>
<12077.1092894555@sss.pgh.pa.us>
Tom,
> This is really interesting. We had previously seen some evidence that
> the Xeon sucks at running Postgres, but I thought that the issues only
> materialized with multiple CPUs (because what we were concerned about
> was the cost of transferring cache lines across CPUs). AFAICS this test
> is using single CPUs. Maybe there is more going on than we realized.
Aside from the fact that the Xeon architecture is a kludge?
Intel really screwed up the whole Xeon line through some bad architectural
decisions, and instead of starting over from scratch, "patched" the problem.
The result has been sub-optimal Xeon performance for the last two years.
This is why AMD is still alive. Better efficiency, lower cost.
--
Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, tgl@sss.pgh.pa.us, wyu@talisys.com
Subject: Re: Help specifying new machine
In-Reply-To: <200408190918.31797.josh@agliodbs.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