From: Jeff <threshar@torgo.978.org>
To: Chris Field <cfield@affinitysolutions.com>
Cc: ron.l.johnson@cox.net
Cc: pgsql-performance@postgresql.org
Subject: Re: Value of Quad vs. Dual Processor machine
Date: Wed, 12 Nov 2003 09:28:07 -0500
Message-ID: <20031112092807.14b18bf4.threshar@torgo.978.org> (raw)
In-Reply-To: <001401c3a8c2$8c8fec30$040210ac@win2000>
References: <1068593567.2063.8.camel@tuxsrva>
<1068600291.30969.53.camel@haggis.homelan>
<001401c3a8c2$8c8fec30$040210ac@win2000>
On Tue, 11 Nov 2003 21:13:19 -0500
"Chris Field" <cfield@affinitysolutions.com> wrote:
> we are looking at Xeon, We are currently running it on a quad sun v880
> compiled to be 64bit and have been getting dreadful performance. I
> don't think we really have much to gain from going 64bit.
>
>
By chance, are you running 7.3.4 on that sun?
If so, try this:
export CFLAGS=-02
./configure
and rebuild PG.
Before 7.4 PG was build with _no_ optimization on Solaris.
Recompiling gives __HUGE__ (notice the underscores) performance gains.
And onto the dual vs quad.
PG will only use 1 cpu / connection / query.
So if your machine iwll have 1-2 queries running at a time those other 2
proc's will sit around idling. However if you are going to have a bunch
going, 4 cpus will be most useful. One of hte nicest things to do for
PG is more ram and fast IO. It really loves those things.
good luck
--
Jeff Trout <jeff@jefftrout.com>
http://www.jefftrout.com/http://www.stuarthamm.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: threshar@torgo.978.org, cfield@affinitysolutions.com, ron.l.johnson@cox.net
Subject: Re: Value of Quad vs. Dual Processor machine
In-Reply-To: <20031112092807.14b18bf4.threshar@torgo.978.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