From: Steinar H. Gunderson <sgunderson@bigfoot.com>
To: pgsql-performance@postgresql.org
Subject: Re: Postgresql and xeon.
Date: Mon, 30 May 2005 18:54:47 +0200
Message-ID: <20050530165447.GA9708@uio.no> (raw)
In-Reply-To: <200505300919.40827.josh@agliodbs.com>
References: <F7B73864DD39FA40B6C56B3CE0D4D1CB634479@asdc003.abovesecurite.lan>
<200505300919.40827.josh@agliodbs.com>
On Mon, May 30, 2005 at 09:19:40AM -0700, Josh Berkus wrote:
> Search the archives of this list. This has been discussed ad nauseum.
> www.pgsql.ru
I must admit I still haven't really understood it -- I know that it appears
on multiple operating systems, on multiple architectures, but most with Xeon
CPUs, and that it's probably related to the poor memory bandwidth between the
CPUs, but that's about it. I've read the threads I could find on the list
archives, but I've yet to see somebody pinpoint exactly what in PostgreSQL is
causing this.
Last time someone claimed this was bascially understood and "just a lot of
work to fix", I asked for pointers to a more detailed analysis, but nobody
answered. Care to explain? :-)
/* Steinar */
--
Homepage: http://www.sesse.net/
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: sgunderson@bigfoot.com
Subject: Re: Postgresql and xeon.
In-Reply-To: <20050530165447.GA9708@uio.no>
* 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