Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 370009FBB1C for ; Wed, 25 Jul 2007 00:16:20 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 72006-01 for ; Wed, 25 Jul 2007 00:16:17 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by postgresql.org (Postfix) with ESMTP id 395149FBA3C for ; Wed, 25 Jul 2007 00:16:17 -0300 (ADT) Received: from [192.168.1.13] (localhost [127.0.0.1]) by FS.denninger.net (8.13.8/8.13.1) with SMTP id l6P3GGGi046248 for ; Tue, 24 Jul 2007 22:16:16 -0500 (CDT) (envelope-from karl@denninger.net) Received: from [192.168.1.13] [192.168.1.13] by Spamblock-sys (LOCAL); Tue Jul 24 22:16:16 2007 Message-ID: <46A6C080.10204@denninger.net> Date: Tue, 24 Jul 2007 22:16:16 -0500 From: Karl Denninger User-Agent: Thunderbird 2.0.0.5 (Windows/20070716) MIME-Version: 1.0 To: Merlin Moncure CC: Tom Lane , pgsql-performance@postgresql.org Subject: Re: Performance issue with 8.2.3 - "C" application References: <46A6A549.1040606@denninger.net> <29633.1185331558@sss.pgh.pa.us> <46A6BBB1.1020502@denninger.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SPAMBLOCK-MATCH: Matched [@postgresql.org+], message ok X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.112 tagged_above=0 required=5 tests=AWL=0.197, BAYES_40=-0.185, RDNS_DYNAMIC=0.1 X-Spam-Level: X-Archive-Number: 200707/330 X-Sequence-Number: 26014 Hmmmmm..... now that's interesting. Stats collector IS accumulating quite a bit of runtime..... me thinks its time to go grab 8.2.4. Karl Denninger (karl@denninger.net) http://www.denninger.net Merlin Moncure wrote: > On 7/25/07, Karl Denninger wrote: >> >> Yeah, the problem doesn't appear to be there. As I said, if I look >> at the >> PS of the system when its bogging, there aren't a whole bunch of >> processes >> stuck doing these, so while this does take a second or two to come back, >> that's not that bad. >> >> Its GENERAL performance that just bites - the system is obviously >> out of >> CPU, but what I can't get a handle on is WHY. It does not appear to be >> accumulating large amounts of runtime in processes I can catch, but >> the load >> average is quite high. > > 8.2.3 has the 'stats collector bug' (fixed in 8.2.4) which increased > load in high concurrency conditions. on a client's machine after > patching the postmaster load drop from the 4-5 range to 1-2 range on a > 500 tps server. maybe this is biting you? symptoms are high load avg > and high cpu usage of stats collector process. > > merlin > > > %SPAMBLOCK-SYS: Matched [google.com+], message ok %SPAMBLOCK-SYS: Matched [@postgresql.org+], message ok