X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 5CE4A3A19AE for ; Mon, 3 Jan 2005 23:44:17 +0000 (GMT) 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 93829-06 for ; Mon, 3 Jan 2005 23:44:06 +0000 (GMT) Received: from net2.micro-automation.com (net2.micro-automation.com [64.7.141.29]) by svr1.postgresql.org (Postfix) with SMTP id 3F77C3A2346 for ; Mon, 3 Jan 2005 23:44:07 +0000 (GMT) Received: (qmail 28966 invoked from network); 3 Jan 2005 23:43:39 -0000 Received: from dcdsl.ebox.com (HELO ?192.168.1.36?) (davec@64.7.143.116) by net2.micro-automation.com with SMTP; 3 Jan 2005 23:43:39 -0000 Message-ID: <41D9D8C1.4090906@fastcrypt.com> Date: Mon, 03 Jan 2005 18:44:01 -0500 From: Dave Cramer Reply-To: pg@fastcrypt.com Organization: Postgres International User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pallav Kalva Cc: Postgres Performance Subject: Re: Very Bad Performance. References: <41D9C4E3.3050001@deg.cc> In-Reply-To: <41D9C4E3.3050001@deg.cc> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.008 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/30 X-Sequence-Number: 9720 Well, it's not quite that simple the rule of thumb is 6-10% of available memory before postgres loads is allocated to shared_buffers. then effective cache is set to the SUM of shared_buffers + kernel buffers Then you have to look at individual slow queries to determine why they are slow, fortunately you are running 7.4 so you can set log_min_duration to some number like 1000ms and then try to analyze why those queries are slow. Also hyperthreading may not be helping you.. Dave Pallav Kalva wrote: > Hi , > > I am experiencing a very bad performance on my production database > lately , all my queries are slowing down. Our application is a > webbased system with lot of selects and updates. I am running > "vacuumdb" daily on all the databases, are the below postgres > configuration parameters are set properly ? can anyone take a look. > Let me know if you need anymore information. > > > Postgres Version: 7.4 > Operating System: Linux Red Hat 9 > Cpus: 2 Hyperthreaded > RAM: 4 gb > Postgres Settings: > max_fsm_pages | 20000 > max_fsm_relations | 1000 > shared_buffers | 65536 > sort_mem | 16384 > vacuum_mem | 32768 > wal_buffers | 64 > effective_cache_size | 393216 > > Thanks! > Pallav > > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster > > -- Dave Cramer http://www.postgresintl.com 519 939 0336 ICQ#14675561