X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 239C9D1B903 for ; Sat, 13 Mar 2004 17:31:22 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 10711-10 for ; Sat, 13 Mar 2004 13:31:19 -0400 (AST) Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) by svr1.postgresql.org (Postfix) with ESMTP id 0A71DD1C4EC for ; Sat, 13 Mar 2004 13:31:19 -0400 (AST) Received: from ool-4352919e.dyn.optonline.net ([67.82.145.158] helo=zeut.net) by outbound.mailhop.org with asmtp (TLSv1:AES256-SHA:256) (Exim 4.20) id 1B2Cyh-000NTT-Eu; Sat, 13 Mar 2004 12:31:15 -0500 Message-ID: <405345F7.7080803@zeut.net> Date: Sat, 13 Mar 2004 12:33:43 -0500 From: "Matthew T. O'Connor" User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joe Conway Cc: Tom Lane , pgsql-performance Subject: Re: rapid degradation after postmaster restart References: <4052661D.5060505@joeconway.com> <18481.1079192379@sss.pgh.pa.us> <405330CD.4050304@joeconway.com> In-Reply-To: <405330CD.4050304@joeconway.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mail-Handler: MailHop Outbound by DynDNS.org X-Report-Abuse-To: abuse@dyndns.org X-MHO-User: Zeut X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/175 X-Sequence-Number: 6031 Joe Conway wrote: > Tom Lane wrote: > >> Just to be clear on this: you have to restart the postmaster to bring >> the time back down? Simply starting a fresh backend session doesn't do >> it? > > > IIRC, shared buffers was reasonable, maybe 128MB. One thing that is > worthy of note is that they are using pg_autovacuum and a very low > vacuum_mem setting (1024). But I also believe that max_fsm_relations > and max_fsm_pages have been bumped up from default (something like > 10000 & 200000). > pg_autovacuum could be a problem if it's vacuuming too often. Have you looked to see if a vacuum or analyze is running while the server is slow? If so, have you played with the pg_autovacuum default vacuum and analyze thresholds? If it appears that it is related to pg_autovacuum please send me the command options used to run it and a logfile of it's output running at at a debug level of -d2 Matthew