Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id B29EE9FA42F for ; Tue, 28 Aug 2007 16:40:15 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 13349-01 for ; Tue, 28 Aug 2007 16:40:10 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from Mercury.turbocorp.com (mercury.turbocorp.com [198.212.166.40]) by postgresql.org (Postfix) with ESMTP id 814249FA42E for ; Tue, 28 Aug 2007 16:40:06 -0300 (ADT) Received: from [198.212.166.61] (Voyager.turbocorp.com [198.212.166.61]) by Mercury.turbocorp.com (8.13.1/8.13.1) with ESMTP id l7SJe3L3022075; Tue, 28 Aug 2007 15:40:03 -0400 Message-ID: <46D47A13.3060907@the-allgoods.net> Date: Tue, 28 Aug 2007 15:40:03 -0400 From: John R Allgood User-Agent: Thunderbird 1.5.0.12 (X11/20070718) MIME-Version: 1.0 To: Alvaro Herrera CC: Tom Lane , pgsql-admin@postgresql.org Subject: Re: How to monitor resources on Linux. References: <46D4353F.2040209@the-allgoods.net> <815.1188324416@sss.pgh.pa.us> <46D470D8.2030605@the-allgoods.net> <20070828191143.GE13868@alvh.no-ip.org> In-Reply-To: <20070828191143.GE13868@alvh.no-ip.org> Content-Type: multipart/alternative; boundary="------------060508010501010509050108" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/359 X-Sequence-Number: 26690 This is a multi-part message in MIME format. --------------060508010501010509050108 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit We are using the defaults for these values. Keep in mind we are allowing between 5-50 max connections per postmaster. Here is an example of our largest database. It is 7.9GB we allow 50 max connections and the buffers are set to 16000/125MB. This is our master database and it has a lot of activity as compared to the other databases. We run VACUUM at midday VACUUM FULL at night, VACUUM ANALYZE on weekends. Thanks Alvaro Herrera wrote: > John R Allgood wrote: > >> Hey Tom >> >> Thanks for responding. This issue came around because of a situation >> yesterday with processes being killed off by the kernel. I believe my co >> worker Geof Myers sent a post yesterday and the response was to adjust the >> vm.commit_memory=2. Several time throughout the day we see memory usage >> peak and then it will go down. We have multiple postmasters running for >> each of our division so that I we have a problem with a database it only >> affects that one. It make it diffucult to tune a system with this many >> postmasters running. Each database is tuned according to need. We allow >> anywhere between 5-50 max connections. So what I am looking for is? >> > > Any of work_mem or maintenance_worm_mem set too high can cause excessive > memory usage. What do you have these set to? > > --------------060508010501010509050108 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit We are using the defaults for these values. Keep in mind we are allowing between 5-50 max connections per postmaster.  Here is an example of our largest database. It is 7.9GB we allow 50 max connections and the buffers are set to 16000/125MB. This is our master database and it has a lot of activity as compared to the other databases. We run VACUUM at midday VACUUM FULL at night, VACUUM ANALYZE on weekends.

Thanks

Alvaro Herrera wrote:
John R Allgood wrote:
  
Hey Tom

   Thanks for responding. This issue came around because of a situation 
yesterday with processes being killed off by the kernel.  I believe my co 
worker Geof Myers sent a post yesterday and the response was to adjust the 
vm.commit_memory=2. Several time throughout the day we see memory usage 
peak and then it will go down. We have multiple postmasters running for 
each of our division so that I we have a problem with a database it only 
affects that one. It make it diffucult to tune a system with this many 
postmasters running. Each database is tuned according to need. We allow 
anywhere between 5-50 max connections. So what I am looking for is?  
    

Any of work_mem or maintenance_worm_mem set too high can cause excessive
memory usage.  What do you have these set to?

  

--------------060508010501010509050108--