From: David Mitchell <david.mitchell@telogis.com>
To: Dennis <dennis@works4me.com>
Cc: Qingqing Zhou <zhouqq@cs.toronto.edu>
Cc: pgsql-performance@postgresql.org
Subject: Re: performance problems ... 100 cpu utilization
Date: Fri, 15 Jul 2005 12:43:07 +1200
Message-ID: <42D7069B.5090107@telogis.com> (raw)
In-Reply-To: <42D60C2E.3020004@works4me.com>
References: <42D567DB.6000100@works4me.com>
<db4l9c$1g4t$1@news.hub.org>
<42D5DBEB.4010503@works4me.com>
<42D5F315.3090301@telogis.com>
<42D60C2E.3020004@works4me.com>
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
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: david.mitchell@telogis.com, dennis@works4me.com, zhouqq@cs.toronto.edu
Subject: Re: performance problems ... 100 cpu utilization
In-Reply-To: <42D7069B.5090107@telogis.com>
* 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