Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 9DDCCB5DC04 for ; Mon, 10 Oct 2011 12:14:44 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 84020-01 for ; Mon, 10 Oct 2011 15:14:38 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0-rc2 Received: from nm15-vm1.bullet.mail.ird.yahoo.com (nm15-vm1.bullet.mail.ird.yahoo.com [77.238.189.194]) by mail.postgresql.org (Postfix) with SMTP id 7EF87B5DBD8 for ; Mon, 10 Oct 2011 12:14:37 -0300 (ADT) Received: from [77.238.189.54] by nm15.bullet.mail.ird.yahoo.com with NNFMP; 10 Oct 2011 15:14:36 -0000 Received: from [212.82.109.128] by tm7.bullet.mail.ird.yahoo.com with NNFMP; 10 Oct 2011 15:14:35 -0000 Received: from [127.0.0.1] by omp1020.mail.ird.yahoo.com with NNFMP; 10 Oct 2011 15:14:35 -0000 X-Yahoo-Newman-Property: ymail-5 X-Yahoo-Newman-Id: 976086.25954.bm@omp1020.mail.ird.yahoo.com Received: (qmail 26401 invoked by uid 60001); 10 Oct 2011 15:14:35 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.it; s=s1024; t=1318259675; bh=Wt7ONmq+Za3EDnElwORVxBZlDWbNoRE5AHMEnwrk+yQ=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=eAUHLlkSUdd+43KRwIv/VnIeLqbrtMocF5EB20sPwmtwUkDwyM06y7u1DTbH0QQuoUTGuKFxh/bUf5yata9PQBmBmgcw2EF3eSdYqwXQIGIhWQ2ehe0fCX5JIf7OHcZdDZwkp40LFos3olcx6SZlVKInGVLqzWlcyeMkBhd4KXQ= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.it; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=SAKTY6yNJVyNjpj7o3oSnRGJfIqUgJjXDtR9H518ChLkDLomwU4Sg3P/XRrgDb0Qch93NwsxiyrFfMHcvXxSt3f+3n6+fkC1IZg9jtHnY0z0izVsnnbTAQe1bnkvuZZm/+Lpp7fzM0878MQ2WWtF0FMrY+OL2UU+stNtgY7j9S8=; X-YMail-OSG: Z7rVC.sVM1ka1KGi7dRELjUSoFE8EdMNZGj5sWEFjQvf8yF FovQQpTA_wLTkJj7AT8s1mzDdgtyZLpon8Rc9uaZagRmKZ7c8USDdlJkIK94 CwtT9GSJxBq9gIVr43L2C5piZRy49kK4lxa.7b.3CEHCUHQaRKOWoqBfAyVs noYR1qF5Ao2nCU1sS1YXlhc8x1gtzX43.Gz8SLSpJZP83372rTdMcsv3EnDr MZMHmZTolVP.UCd2_XitcGzY_ouSrA4Cnt420maFxMMPeZU8sLmPsI6XjNv8 MNVcT6xm8KwidiCSyD_9mDqBtiO304lbiMGxcLBHBz3_DJjetG.uaRDzzpIb FphlIzHibzJGVIHXCOhnsbbyoY2U9MU7au0tdZgtPcRfzCUcgTvdgAEwUVhd j_nY- Received: from [85.33.62.89] by web29011.mail.ird.yahoo.com via HTTP; Mon, 10 Oct 2011 16:14:35 BST X-Mailer: YahooMailWebService/0.8.114.317681 References: <4E92F294.9010405@gmail.com> <4E92FB87.1030703@peak6.com> Message-ID: <1318259675.10344.YahooMailNeo@web29011.mail.ird.yahoo.com> Date: Mon, 10 Oct 2011 16:14:35 +0100 (BST) From: Leonardo Francalanci Reply-To: Leonardo Francalanci Subject: Re: Adding more memory = hugh cpu load To: "sthomas@peak6.com" , alexandre - aldeia digital Cc: "pgsql-performance@postgresql.org" In-Reply-To: <4E92FB87.1030703@peak6.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.899 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201110/80 X-Sequence-Number: 45302 =0A=0A> That's not entirely surprising. The problem with having lots of mem= ory is... =0A> that you have lots of memory. The operating system likes to = cache, and this =0A> includes writes. Normally this isn't a problem, but wi= th 48GB of RAM, the =0A> defaults (for CentOS 5.5 in particular) are to use= up to 40% of that to cache =0A> writes.=0A=0A=0AI don't understand: don't = you want postgresql to issue the fsync calls when=0Ait "makes sense" (and c= onfigure them), rather than having the OS decide=0Awhen it's best to flush = to disk? That is: don't you want all the memory to=0Abe used for caching, u= nless postgresql says otherwise (calling fsync), instead=0Aof "as soon as 1= % of memory is used"?=0A