Re: Stats collector eats my CPU

No. The only side effects is constant CPU load on this level (15%)
regardless if there is DB activity or no. The machine is 2*quad so 15
of 800 isn't really much - but I afraid what will be, if I'll get more
significant traffic there.

As you mentioned the total time summary is the effect of uptime which
is about half a year now.

> 2008/10/8 Wojciech Strzałka <wstrzalka(at)gmail(dot)com>:
>>
>> For clarification 250k is total relation count.
>> There is 85k plain tables + 45k toasts.
>>
>> Except stats collector overload, the cluster works fine ( no really
>> surprising, while we are using world best database :D )

> Couple of other points here:
> *) stats collector process is very long lived and does things, so will
> accumulate cpu time according to top over the shorter lived backend
> connections
> *) most servers are multi core these days...stats will eat at most one core

> maybe this is a non-problem? are you seeing other issues outside of
> high cpu time according to top?

> merlin

--
Pozdrowienia,
Wojciech Strzałka