pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Karl Denninger <karl@denninger.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Merlin Moncure <mmoncure@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance issue with 8.2.3 - "C" application
Date: Wed, 25 Jul 2007 16:01:28 -0500
Message-ID: <46A7BA28.5030203@denninger.net> (raw)
In-Reply-To: <46A6C50D.1000908@denninger.net>
References: <46A6A549.1040606@denninger.net>
	<29633.1185331558@sss.pgh.pa.us>
	<46A6BBB1.1020502@denninger.net>
	<b42b73150707242015k615c7018s75cc0b804dbb5677@mail.gmail.com>
	<46A6C080.10204@denninger.net>
	<122.1185333906@sss.pgh.pa.us>
	<46A6C50D.1000908@denninger.net>

Looks like that was the problem - got a day under the belt now with the 
8.2.4 rev and all is back to normal.

Karl Denninger (karl@denninger.net)
http://www.denninger.net




Karl Denninger wrote:
> Aha!
>
> BIG difference.  I won't know for sure until the biz day tomorrow but 
> the "first blush" look is that it makes a HUGE difference in system 
> load, and I no longer have the stats collector process on the top of 
> the "top" list......
>
> Karl Denninger (karl@denninger.net)
> http://www.denninger.net
>
>
>
>
> Tom Lane wrote:
>> Karl Denninger <karl@denninger.net> writes:
>>  
>>> Hmmmmm..... now that's interesting.  Stats collector IS accumulating 
>>> quite a bit of runtime..... me thinks its time to go grab 8.2.4.
>>>     
>>
>> I think Merlin might have nailed it --- the "stats collector bug" is
>> that it tries to write out the stats file way more often than it
>> should.  So any excessive userland CPU time you see is just the tip
>> of the iceberg compared to the system and I/O costs incurred.
>>
>>             regards, tom lane
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 1: if posting/reading through Usenet, please send an appropriate
>>        subscribe-nomail command to majordomo@postgresql.org so that your
>>        message can get through to the mailing list cleanly
>>
>>
>> %SPAMBLOCK-SYS: Matched [hub.org+], message ok
>>   
>
>
> %SPAMBLOCK-SYS: Matched [@postgresql.org+], message ok
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
>
> %SPAMBLOCK-SYS: Matched [hub.org+], message ok


%SPAMBLOCK-SYS: Matched [@postgresql.org+], message ok



view thread (10+ messages)

Message-ID: <46A7BA28.5030203@denninger.net>
Permalink:  ../46A7BA28.5030203@denninger.net/
Also on:    postgresql.org/message-id/46A7BA28.5030203@denninger.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: karl@denninger.net, tgl@sss.pgh.pa.us, mmoncure@gmail.com
  Subject: Re: Performance issue with 8.2.3 - "C" application
  In-Reply-To: <46A7BA28.5030203@denninger.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox