Re: performance problems ... 100 cpu utilization

From: David Mitchell <david(dot)mitchell(at)telogis(dot)com>
To: Dennis <dennis(at)works4me(dot)com>
Cc: Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-performance(at)postgresql(dot)org
Subject: Re: performance problems ... 100 cpu utilization
Date: 2005-07-15 00:43:07
Message-ID: 42D7069B.5090107@telogis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

If your table has got into this state, then vacuum analyze won't fix it.
You will have to do a vacuum full to get it back to normal, then
regularly vacuum (not full) to keep it in good condition. We vacuum our
critical tables every 10 minutes to keep them in good nick.

David

Dennis wrote:
> David Mitchell wrote:
>
>> What is the load average on this machine? Do you do many updates? If
>> you do a lot of updates, perhaps you haven't vacuumed recently. We
>> were seeing similar symptoms when we started load testing our stuff
>> and it turned out we were vacuuming too infrequently.
>
>
> The load average at the 100% utilization point was about 30! A vacuum
> analyze was done before the test was started. I believe there are many
> more selects than updates happening at any one time.
>
> Dennis
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
>

--
David Mitchell
Software Engineer
Telogis

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Alison Winters 2005-07-15 02:26:09 Re: lots of updates on small table
Previous Message Alvaro Herrera 2005-07-15 00:37:30 Re: lots of updates on small table