pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: aturner@neteconomist.com
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Richard Huxton <dev@archonet.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Upgrade Woes
Date: Thu, 11 Sep 2003 15:10:18 -0400
Message-ID: <20030911191018.GA11764@neteconomist.com> (raw)
In-Reply-To: <27548.1063295252@sss.pgh.pa.us>
References: <20030910175340.GC5506@neteconomist.com>
	<200309101931.53746.dev@archonet.com>
	<20030911141622.GB26759@neteconomist.com>
	<27548.1063295252@sss.pgh.pa.us>

In the performance case the machine was running RedHat AS 2.1.  I have posted the database schema at (obtained from pg_dump -s):

http://serverbeach.plexq.com/~aturner/schema.sql

The time to run all the stats procedures dropped through the floor.  refresh_hourly_iud, adl_hourly_iud, rebuild_daily_total etc.  There is a python script that calls the proc once for each hour or day.  When running the historical calc job for a 7 day period back, it would crawl on 7.3.3.  We started benching the drive array and found other issues with the system in the mean time (like the drive array was giving us 10MB/sec write speed - the guy who set it up did not enable write to cache).  Once it was reconfigured the DB performance did not improve much (bonnie++ was used to verify the RAID array speed).

Alex Turner

On Thu, Sep 11, 2003 at 11:47:32AM -0400, Tom Lane wrote:
> aturner@neteconomist.com writes:
> > As for 7.3.3, the project in question suffered a 10x performance
> > degredation on 7.3.3 which went away when we rolled back to 7.3.2.
> 
> I would like to pursue that report and find out why.  I've just gone
> through the CVS logs between 7.3.2 and 7.3.3, and I don't see any change
> that would explain a 10x slowdown.  Can you provide more details about
> exactly what slowed down?
> 
> Also, what PG version were you using on the old RedHat 7.2 installation?
> 
> 			regards, tom lane



view thread (7+ messages)

Message-ID: <20030911191018.GA11764@neteconomist.com>
Permalink:  ../20030911191018.GA11764@neteconomist.com/
Also on:    postgresql.org/message-id/20030911191018.GA11764@neteconomist.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: aturner@neteconomist.com, tgl@sss.pgh.pa.us, dev@archonet.com
  Subject: Re: Upgrade Woes
  In-Reply-To: <20030911191018.GA11764@neteconomist.com>
  References: <20030910175340.GC5506@neteconomist.com> <200309101931.53746.dev@archonet.com> <20030911141622.GB26759@neteconomist.com> <27548.1063295252@sss.pgh.pa.us> <20030911191018.GA11764@neteconomist.com>

* 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