Received: from localhost (unknown [200.46.204.183])
	by postgresql.org (Postfix) with ESMTP id 25C3265050F
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Sat, 12 Jul 2008 08:30:47 -0300 (ADT)
Received: from postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 99536-06 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Sat, 12 Jul 2008 08:30:39 -0300 (ADT)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from web56401.mail.re3.yahoo.com (web56401.mail.re3.yahoo.com
	[216.252.111.80])
	by postgresql.org (Postfix) with SMTP id AE43F65050B
	for <pgsql-performance@postgresql.org>;
	Sat, 12 Jul 2008 08:30:43 -0300 (ADT)
Received: (qmail 64442 invoked by uid 60001); 12 Jul 2008 11:30:42 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
	b=QOOuJ3WyMrO+guATaG2BXNIMChbPSX1JEVLJxtlJLJ1Pigj4Ae35pmjTDGFkzqro0EkGVBlSp/kE6KiTB1le7LSsdNJwbey2hXylOX2S0G8OkP9lnlRIBdFsJrCaL7eBh4e72SrBGZig0krwMPd6E/4yM7NU7jV/py9XHyEu6Xc=;
Received: from [98.166.112.215] by web56401.mail.re3.yahoo.com via HTTP;
	Sat, 12 Jul 2008 04:30:42 PDT
X-Mailer: YahooMailRC/1042.40 YahooMailWebService/0.7.218
Date: Sat, 12 Jul 2008 04:30:42 -0700 (PDT)
From: Jessica Richard <rjessil@yahoo.com>
Subject: how to estimate shared_buffers...
To: pgsql-performance@postgresql.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-489930958-1215862242=:43246"
Message-ID: <93721.43246.qm@web56401.mail.re3.yahoo.com>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.001 tagged_above=0 required=5
	tests=HTML_MESSAGE=0.001
X-Spam-Level: 
X-Archive-Number: 200807/115
X-Sequence-Number: 30715

--0-489930958-1215862242=:43246
Content-Type: text/plain; charset=us-ascii

On a running production machine, we have 900M configured on a 16G-memory Linux host. The db size for all dbs combined is about 50G.  There are many transactions going on all the times (deletes, inserts, updates). We do not have a testing environment that has the same setup and the same amount of workload. I want to evaluate on the production host if this 900M is enough. If not, we still have room to go up a little bit to speed up all Postgres activities. I don't know enough about the SA side. I just would imagine, if something like "top" command or other tools can measure how much total memory Postgres is actually using (against the configured 900M shared buffers), and if Postgres is using almost 900M all the time, I would take this as an indication that the shared_buffers can go up for another 100M...

What is the best way to tell how much memory Postgres (all Postgres related things) is actually using?

Thanks
Jessica



      
--0-489930958-1215862242=:43246
Content-Type: text/html; charset=us-ascii

<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div>On a running production machine, we have 900M configured on a 16G-memory Linux host. The db size for all dbs combined is about 50G.&nbsp; There are many transactions going on all the times (deletes, inserts, updates). We do not have a testing environment that has the same setup and the same amount of workload. I want to evaluate on the production host if this 900M is enough. If not, we still have room to go up a little bit to speed up all Postgres activities. I don't know enough about the SA side. I just would imagine, if something like "top" command or other tools can measure how much total memory Postgres is actually using (against the configured 900M shared buffers), and if Postgres is using almost 900M all the time, I would take this as an indication that the shared_buffers can go up
 for another 100M...<br><br>What is the best way to tell how much memory Postgres (all Postgres related things) is actually using?<br><br>Thanks<br>Jessica<br></div></div><br>

      </body></html>
--0-489930958-1215862242=:43246--