pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Robert Treat <xzilla@users.sourceforge.net>
To: Jeff <threshar@torgo.978.org>
Cc: 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: 13 Nov 2003 10:52:25 -0500
Message-ID: <1068738745.10945.18380.camel@camel> (raw)
In-Reply-To: <20031112092807.14b18bf4.threshar@torgo.978.org>
References: <1068593567.2063.8.camel@tuxsrva>
	<1068600291.30969.53.camel@haggis.homelan>
	<001401c3a8c2$8c8fec30$040210ac@win2000>
	<20031112092807.14b18bf4.threshar@torgo.978.org>

On Wed, 2003-11-12 at 09:28, Jeff wrote:
> 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.
> 

We've just started kicking around the idea of moving one of our boxes to
a quad-proc machine from a dual. Under normal circumstances the 2
processors handle maybe 200 transactions per second with 90% system
idle.  However we have people who occasionally run historical reports on
our data, and those reports are fairly CPU intensive. Usually it is not
a problem for the main web system, but when pg_dump is running, that is
also cpu intensive, so we end up with two highly cpu intensive items
running on our machine, and we start to notice issues on the main web
system. 
  

Robert Treat
-- 
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL




view thread (12+ messages)

Message-ID: <1068738745.10945.18380.camel@camel>
Permalink:  ../1068738745.10945.18380.camel@camel/
Also on:    postgresql.org/message-id/1068738745.10945.18380.camel@camel

 · 

reply

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: xzilla@users.sourceforge.net, threshar@torgo.978.org, cfield@affinitysolutions.com, ron.l.johnson@cox.net
  Subject: Re: Value of Quad vs. Dual Processor machine
  In-Reply-To: <1068738745.10945.18380.camel@camel>

* 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