From: Alan Hodgson <ahodgson@reinvent.com>
To: pgsql-performance@postgresql.org
Subject: Re: Occasional giant spikes in CPU load
Date: Wed, 7 Apr 2010 16:38:27 -0700
Message-ID: <201004071638.27421@hal.medialogik.com> (raw)
In-Reply-To: <4BBD0DD5.3050807@emolecules.com>
References: <k2pda0294261004061437p9cd3810dqe9ce528b6ddb0873@mail.gmail.com>
<1270679808.19131.28.camel@jd-desktop.unknown.charter.com>
<4BBD0DD5.3050807@emolecules.com>
On Wednesday 07 April 2010, Craig James <craig_james@emolecules.com> wrote:
> I thought so too, except that I can't login during the flood. If the
> CPUs were all doing iowaits, logging in should be easy.
Busying out the drives is about the most reliable way to make logging in
very slow (especially, but not only, if it's due to swapping).
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: ahodgson@reinvent.com
Subject: Re: Occasional giant spikes in CPU load
In-Reply-To: <201004071638.27421@hal.medialogik.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