From: Josh Berkus <josh@agliodbs.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Frank Knobbe <frank@knobbe.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: postgres 7.4 at 100%
Date: Mon, 28 Jun 2004 09:47:59 -0700
Message-ID: <200406280947.59420.josh@agliodbs.com> (raw)
In-Reply-To: <17884.1088399982@sss.pgh.pa.us>
References: <e071108e04062423591d2b8aa9@mail.gmail.com>
<1088397641.1105.10.camel@localhost>
<17884.1088399982@sss.pgh.pa.us>
Tom,
> So while he surely should not go back to 40, it seems there's another
> factor involved here that we've not recognized yet.
I'd agree. Actually, the first thing I'd do, were it my machine, is reboot it
and run memtest86 overnight. CPU thrashing like that may indicate bad RAM.
If the RAM checks out, I'd like to see the EXPLAIN ANALYZE for some of the
longest-running queries, and for those INSERTS.
Also, is the new machine running Software RAID?
--
Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, tgl@sss.pgh.pa.us, frank@knobbe.us
Subject: Re: postgres 7.4 at 100%
In-Reply-To: <200406280947.59420.josh@agliodbs.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