From: Tom Lane <tgl@sss.pgh.pa.us>
To: Fabio Esposito <nfesposi@sourceweave.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: postgres eating CPU on HP9000
Date: Fri, 26 Mar 2004 16:53:40 -0500
Message-ID: <27627.1080338020@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.44.0403231318150.17978-100000@cr818510-a.basement>
References: <Pine.LNX.4.44.0403231318150.17978-100000@cr818510-a.basement>
Fabio Esposito <nfesposi@sourceweave.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
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: tgl@sss.pgh.pa.us, nfesposi@sourceweave.net
Subject: Re: postgres eating CPU on HP9000
In-Reply-To: <27627.1080338020@sss.pgh.pa.us>
* 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