Skip site navigation (1) Skip section navigation (2)

Re: Postgresql and xeon.

From: "Eric Lauzon" <eric(dot)lauzon(at)abovesecurity(dot)com>
To: "Steinar H(dot) Gunderson" <sgunderson(at)bigfoot(dot)com>,<pgsql-performance(at)postgresql(dot)org>
Subject: Re: Postgresql and xeon.
Date: 2005-05-30 17:02:12
Message-ID: F7B73864DD39FA40B6C56B3CE0D4D1CB63447B@asdc003.abovesecurite.lan (view raw or flat)
Thread:
Lists: pgsql-performance

> -----Original Message-----
> From: pgsql-performance-owner(at)postgresql(dot)org 
> [mailto:pgsql-performance-owner(at)postgresql(dot)org] On Behalf Of 
> Steinar H. Gunderson
> Sent: 30 mai 2005 12:55
> To: pgsql-performance(at)postgresql(dot)org
> Subject: Re: [PERFORM] Postgresql and xeon.
> 
> 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? :-)

Same here archives references are just overview but no real data....
to where and why, i would state pg 7.4.8 and kernel 2.6 with preemptive scheduler
and dual xeon 3.2 ghz 6 gig of ram.


Eric Lauzon
[Recherche & Développement]
Above Sécurité / Above Security
Tél  : (450) 430-8166
Fax : (450) 430-1858 

pgsql-performance by date

Next:From: Tobias BroxDate: 2005-05-30 17:08:16
Subject: Re: timestamp indexing
Previous:From: Steinar H. GundersonDate: 2005-05-30 16:54:47
Subject: Re: Postgresql and xeon.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group