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 73160D9DE0 for ; Wed, 9 Nov 2005 17:24:54 -0400 (AST) 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 93400-09 for ; Wed, 9 Nov 2005 21:24:49 +0000 (GMT) X-Greylist: delayed 02:58:33.844077 by SQLgrey- Received: from pop-tawny.atl.sa.earthlink.net (pop-tawny.atl.sa.earthlink.net [207.69.195.67]) by svr1.postgresql.org (Postfix) with ESMTP id 8D13CD9AE8 for ; Wed, 9 Nov 2005 17:24:49 -0400 (AST) Received: from elwamui-hound.atl.sa.earthlink.net ([209.86.224.34]) by pop-tawny.atl.sa.earthlink.net with esmtp (Exim 3.36 #10) id 1EZxR3-0005bY-00; Wed, 09 Nov 2005 16:24:49 -0500 Message-ID: <17035565.1131571489652.JavaMail.root@elwamui-hound.atl.sa.earthlink.net> Date: Wed, 9 Nov 2005 16:24:49 -0500 (EST) From: Ron Peacetree Reply-To: Ron Peacetree To: Yves Vindevogel , pgsql-performance@postgresql.org Subject: Re: Some help on buffers and other performance tricks Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailer: EarthLink Zoo Mail 1.0 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.31 required=5 tests=[AWL=-0.169, DNS_FROM_RFC_ABUSE=0.479] X-Spam-Score: 0.31 X-Spam-Level: X-Archive-Number: 200511/162 X-Sequence-Number: 15419 0=3D Optimize your schema to be a tight as possible. Your goal is to give = yourself the maximum chance that everything you want to work on is in RAM w= hen you need it. 1=3D Upgrade your RAM to as much as you can possibly strain to afford. 4GB= at least. It's that important. 2=3D If the _entire_ DB does not fit in RAM after upgrading your RAM, the n= ext step is making sure your HD IO subsystem is adequate to your needs. 3=3D Read the various pg tuning docs that are available and Do The Right Th= ing. 4=3D If performance is still not acceptable, then it's time to drill down i= nto what specific actions/queries are problems. If you get to here and the entire DBMS is still not close to acceptable, yo= ur fundamental assumptions have to be re-examined. Ron -----Original Message----- From: Yves Vindevogel Sent: Nov 9, 2005 3:11 PM To: pgsql-performance@postgresql.org Subject: [PERFORM] Some help on buffers and other performance tricks Hi all, I've got PG 8.0 on Debian sarge set up ... I want to speed up performance on the system. The system will run PG, Apache front-end on port 80 and Tomcat / Cocoon=20 for the webapp. The webapp is not so heavily used, so we can give the max performance=20 to the database. The database has a lot of work to do, we upload files every day. The current server has 8 databases of around 1 million records. This=20 will be more in the future. There's only one main table, with some smaller tables. 95% of the=20 records are in that one table. A lot of updates are done on that table, affecting 10-20% of the=20 records. The system has 1 gig of ram. I could give 512Mb to PG. Filesystem is ext2, with the -noatime parameter in fstab Could I get some suggestions in how to configure my buffers, wals, ....=20 ? Met vriendelijke groeten, Bien =EF=BF=BD vous, Kind regards, Yves Vindevogel Implements