Received: from mail.perdue.net (c696732-a.west1.ia.home.com [24.22.227.157]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f35CsQ823162 for ; Thu, 5 Apr 2001 08:54:26 -0400 (EDT) (envelope-from tperdue@mail.perdue.net) Received: (from tperdue@localhost) by mail.perdue.net (8.11.2/8.11.2/Debian 8.11.2-1) id f35Cqoc20084; Thu, 5 Apr 2001 07:52:50 -0500 Date: Thu, 5 Apr 2001 07:52:50 -0500 From: Tim Perdue To: Tom Lane Cc: pgsql-sql@postgresql.org Subject: Re: Memory and performance Message-ID: <20010405075250.H513@mail.perdue.net> References: <200104041715.f34HF8858323@postgresql.org> <14398.986435610@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.12i In-Reply-To: <14398.986435610@sss.pgh.pa.us>; from tgl@sss.pgh.pa.us on Wed, Apr 04, 2001 at 09:53:30PM -0400 X-Archive-Number: 200104/77 X-Sequence-Number: 2417 I thought this was an interesting thread because we're running into problems with IO under 7.1 during vacuum and a couple of scheduled aggregation jobs. Our database is about 1GB in total size, the machine has 4GB, but the entire system is only using 1.2 GB, even during vacuum or a daily, extremely large query that requires a lot of grouping and sorting. Any suggestions as to how we can make more use of our RAM, paricularly during vacuum, which is when we get killed? We've actually considered mounting the database on a RAM drive in a halfway serious way. Tim -- Founder - PHPBuilder.com / Geocrawler.com Lead Developer - SourceForge VA Linux Systems