Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 66BE8632EFE for ; Wed, 7 Apr 2010 20:53:19 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 52924-02 for ; Wed, 7 Apr 2010 23:53:01 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-gw0-f46.google.com (mail-gw0-f46.google.com [74.125.83.46]) by mail.postgresql.org (Postfix) with ESMTP id 7F25C632A45 for ; Wed, 7 Apr 2010 20:53:08 -0300 (ADT) Received: by gwb19 with SMTP id 19so836371gwb.19 for ; Wed, 07 Apr 2010 16:53:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:received:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=na2fzI1PjH2dXIic2dDzJjMLT+ou0NnlracxxhEIlYg=; b=QqqBBay2IgaTfK/mjPYbLwYixF+vO3TqcAXNk82CyFby3uvXsljJtYqsHlcwOvzH2b MkLU7rY5XOxyci9+RcLh6U2BqhQEETUl2hAeww6rZ/Mbc9vb+hRU/fXINofB77q1M7ip Vg7pNLDDmVFFGnmEUau/cgyT44ZDGpq1aw9pA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=ZWDQPcJcc3SCyq61frdKW05D8E7He5MkVBk7ULYsgqT3YosWkD3BhWXNVTy/DdAYLz Q8STP4cJSWe+TxBM9skDpY40WqgxZ96n0qpT6T7xpzMdCAlKoHX7DYrQ3yQLy6EUK2s8 0lBmCYB6Pz8xBdsKOSHW4ATzQw3coj4x4klsI= MIME-Version: 1.0 Received: by 10.151.111.5 with HTTP; Wed, 7 Apr 2010 16:52:47 -0700 (PDT) In-Reply-To: <4BBD0DD5.3050807@emolecules.com> References: <4BBCFB12.1010306@emolecules.com> <1270676410.19131.21.camel@jd-desktop.unknown.charter.com> <4BBCFCDE.5020405@emolecules.com> <1270679808.19131.28.camel@jd-desktop.unknown.charter.com> <4BBD0DD5.3050807@emolecules.com> From: David Rees Date: Wed, 7 Apr 2010 16:52:47 -0700 Received: by 10.151.86.1 with SMTP id o1mr6316291ybl.279.1270684387218; Wed, 07 Apr 2010 16:53:07 -0700 (PDT) Message-ID: Subject: Re: Occasional giant spikes in CPU load To: Craig James Cc: jd@commandprompt.com, pgsql-performance@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=-10 required=5 tests=BAYES_50=0.001 X-Spam-Level: X-Archive-Number: 201004/82 X-Sequence-Number: 38332 On Wed, Apr 7, 2010 at 3:57 PM, Craig James wr= ote: > On 4/7/10 3:36 PM, Joshua D. Drake wrote: >> My guess is that it is not CPU, it is IO and your CPU usage is all WAIT >> on IO. >> >> To have your CPUs so flooded that they are the cause of an inability to >> log in is pretty suspect. > > I thought so too, except that I can't login during the flood. =A0If the C= PUs > were all doing iowaits, logging in should be easy. No - logging in with high iowait is very harder to do than high CPU time because of latency of disk access. > Greg's suggestion that shared_buffers and work_mem are too big for an 8 G= B > system fits these symptoms -- if it's having a swap storm, login is > effectively impossible. A swap storm effectively puts the machine into very high iowait time. -Dave