X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 7B608D9F4A for ; Mon, 10 Oct 2005 18:54:56 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 85516-04 for ; Mon, 10 Oct 2005 21:54:53 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 9AA2DD9ED1 for ; Mon, 10 Oct 2005 18:54:54 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j9ALsnuE006248; Mon, 10 Oct 2005 17:54:49 -0400 (EDT) To: Jon Brisbin Cc: pgsql-performance@postgresql.org Subject: Re: Performance on SUSE w/ reiserfs In-reply-to: <434ADD46.5060206@npcinternational.com> References: <434ADD46.5060206@npcinternational.com> Comments: In-reply-to Jon Brisbin message dated "Mon, 10 Oct 2005 16:29:42 -0500" Date: Mon, 10 Oct 2005 17:54:49 -0400 Message-ID: <6247.1128981289@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 required=5 tests=[AWL=0.006] X-Spam-Level: X-Archive-Number: 200510/174 X-Sequence-Number: 14942 Jon Brisbin writes: > I have a SUSE 9 box that is running Postgres 8.0.1 compiled from source. > Over time, I see the memory usage of the box go way way up (it's got > 8GBs in it and by the end of the day, it'll be all used up) with what > looks like cached inodes relating to the extreme IO generated by > postgres. We replicate about 10GBs of data every day from our AS/400 > into postgres, and it is the main database for our intranet portal, > which will server 40,000 pages on a good day. Are you sure it's not cached data pages, rather than cached inodes? If so, the above behavior is *good*. People often have a mistaken notion that having near-zero free RAM means they have a problem. In point of fact, that is the way it is supposed to be (at least on Unix-like systems). This is just a reflection of the kernel doing what it is supposed to do, which is to use all spare RAM for caching recently accessed disk pages. If you're not swapping then you do not have a problem. You should be looking at swap I/O rates (see vmstat or iostat) to determine if you have memory pressure, not "free RAM". regards, tom lane