From: Alan Hodgson <ahodgson@simkin.ca>
To: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL performance issues
Date: Wed, 30 Aug 2006 09:24:26 -0700
Message-ID: <200608300924.26151@hal.medialogik.com> (raw)
In-Reply-To: <44F56CE9.6060602@studentvillage.co.za>
References: <44F446B2.2090900@studentvillage.co.za>
<9A079B52-0D1D-4682-A841-AA856439698E@infogears.com>
<44F56CE9.6060602@studentvillage.co.za>
On Wednesday 30 August 2006 03:48, Willo van der Merwe
<willo@studentvillage.co.za> wrote:
> Hi Rusty,
>
> Good ideas and I've implemented some of them, and gained about 10%. I'm
> still sitting on a load avg of about 60.
>
> Any ideas on optimizations on my postgresql.conf, that might have an
> effect?
If all of those sessions are truly doing a select count(*) from a .75
million row table (plus half a million dead rows), then I'm not suprised
it's bogged down. Every query has to loop through the cache of the full
table in memory every time it's run.
Your CPU is doing something. I doubt that postgresql.conf settings are
going to help. What exactly are all those high CPU usage sessions doing?
--
"Government big enough to supply everything you need is big enough to take
everything you have ... the course of history shows that as a government
grows, liberty decreases." -- Thomas Jefferson
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: ahodgson@simkin.ca
Subject: Re: PostgreSQL performance issues
In-Reply-To: <200608300924.26151@hal.medialogik.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