From: 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 01:49:15 -0400
Message-ID: <12077.1092894555@sss.pgh.pa.us> (raw)
In-Reply-To: <cg1a6d$2aml$1@news.hub.org>
References: <20040809165657.GB15169@campbell-lange.net>
<cfgq0v$29k8$1@news.hub.org>
<cfhmvr$1k4o$1@news.hub.org>
<cfofug$2opb$1@news.hub.org>
<cfvrsk$gf2$1@news.hub.org>
<cg1a6d$2aml$1@news.hub.org>
William Yu <wyu@talisys.com> writes:
> In terms of Postgres database performance, Opteron *may* be the better
> CPU for this app but there's not enough data points yet. Here's a recent
> review at Anandtech showing Opteron 150 (2.4ghz) versus 64-bit Prescott
> 3.6hgz with some very simple MySQL and Postgres benchmarks:
> http://www.anandtech.com/linux/showdoc.aspx?i=2163&p=2> What is a slight lead in MySQL becomes a blowout in Postgres.
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.
regards, tom lane
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: tgl@sss.pgh.pa.us, wyu@talisys.com
Subject: Re: Help specifying new machine
In-Reply-To: <12077.1092894555@sss.pgh.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