Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id E2C7BB5DBD6 for ; Tue, 11 Oct 2011 08:54:52 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 03582-07 for ; Tue, 11 Oct 2011 11:54:46 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0-rc2 Received: from mail-yw0-f46.google.com (mail-yw0-f46.google.com [209.85.213.46]) by mail.postgresql.org (Postfix) with ESMTP id 3A34DB5DBCA for ; Tue, 11 Oct 2011 08:54:46 -0300 (ADT) Received: by ywb5 with SMTP id 5so6430014ywb.19 for ; Tue, 11 Oct 2011 04:54:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=onibYlchi8P0DRXniDzxwx6OzSKodv82r8KPZHk+9r0=; b=sWfA4nnVOnX81HfyoNH0nX9veEN++nD3s0iqn5cX7Ry77PKCdcYog2ikVzBV40P+Le Hkaw+sQV0w/jBFm/DQ79ngMS1dA5xmVrH5A0kRdZQ9peFKfQIoi4opvbm1R0VxrIOSkA 65tKwd5Tc9tv4RUyGZBY6vvCqihTnaRcrxw5Y= Received: by 10.100.254.2 with SMTP id b2mr4503670ani.138.1318334086204; Tue, 11 Oct 2011 04:54:46 -0700 (PDT) Received: from [192.168.1.215] ([177.35.194.80]) by mx.google.com with ESMTPS id 18sm61641392any.21.2011.10.11.04.54.44 (version=SSLv3 cipher=OTHER); Tue, 11 Oct 2011 04:54:44 -0700 (PDT) Message-ID: <4E942E82.9010307@gmail.com> Date: Tue, 11 Oct 2011 08:54:42 -0300 From: alexandre - aldeia digital User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15 MIME-Version: 1.0 CC: pgsql-performance@postgresql.org Subject: Re: Adding more memory = hugh cpu load References: <4E92F294.9010405@gmail.com> <4E92FB87.1030703@peak6.com> <4E932BFC.7070007@gmail.com> <4E92E9340200002500041CD5@gw.wicourts.gov> <4E933F4B.2080808@gmail.com> <4E9303A00200002500041CFE@gw.wicourts.gov> <4E9356E5.6000308@gmail.com> <4E9314A50200002500041D12@gw.wicourts.gov> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.868 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, MISSING_HEADERS=1.021, T_TO_NO_BRKTS_FREEMAIL=0.01 X-Spam-Level: X-Archive-Number: 201110/98 X-Sequence-Number: 45320 Em 10-10-2011 23:19, Claudio Freire escreveu: > On Tue, Oct 11, 2011 at 12:02 AM, Samuel Gendler > wrote: >> The original question doesn't actually say that performance has gone down, >> only that cpu utilization has gone up. Presumably, with lots more RAM, it is >> blocking on I/O a lot less, so it isn't necessarily surprising that CPU >> utilization has gone up. The only problem would be if db performance has >> gotten worse. Maybe I missed a message where that was covered? I don't see >> it in the original query to the list. > > Load average (which is presumably the metric in question) includes > both processes using the CPU and processes waiting for I/O. > So it *would* be strange for load average to go up like that, if > database configuration remains the same (ie: equal query plans) Yep, that's the point. Iostat and vmstat reports a very low use of the disks (lower than before the changes are made - perhaps because the cache). Nothing changed in database itself.