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

Re: postgres eating CPU on HP9000

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fabio Esposito <nfesposi(at)sourceweave(dot)net>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: postgres eating CPU on HP9000
Date: 2004-03-26 21:53:40
Message-ID: 27627.1080338020@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
Fabio Esposito <nfesposi(at)sourceweave(dot)net> writes:
> We've recently integrated postgres into an existing mature app.  Its a
> time sensitive 24x7 system.  It runs on HP9000, a K370 Dual Processor
> system.  Postgres is version 7.3.2.  Its spawned as a child from a parent
> supervisory process, and they communicate to eachother via shared memory.

You would be well advised to update to 7.3.6, though I'm not sure if any
of the post-7.3.2 fixes have anything to do with your speed problem.

> Recently it started eating up the cpu, and cannot keepup with the system
> like it used to.  The interesting thing here is that it still runs great
> on an older system with less ram, one slower cpu, and an older disk.

> We tried the following with no success:

> running VACCUUM FULL
> dropping all tables and staring anew

Did you start from a fresh initdb, or just drop and recreate user
tables?  I'm wondering about index bloat on the system tables ...

			regards, tom lane

In response to

pgsql-performance by date

Next:From: scott.marloweDate: 2004-03-26 22:17:51
Subject: Re: postgres eating CPU on HP9000
Previous:From: Andrew RawnsleyDate: 2004-03-26 18:15:21
Subject: Re: column size too large, is this a bug?

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