pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Willo van der Merwe <willo@studentvillage.co.za>
To: Dave Dutcher <dave@tridecap.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL performance issues
Date: Wed, 30 Aug 2006 16:48:57 +0200
Message-ID: <44F5A559.9050701@studentvillage.co.za> (raw)
In-Reply-To: <007501c6cc3d$01e1e290$8300a8c0@tridecap.com>
References: <007501c6cc3d$01e1e290$8300a8c0@tridecap.com>

Dave Dutcher wrote:
> That's an interesting situation.  Your CPU's are pegged, and you're 
> hardly doing any IO.  I wonder if there is some ineficient query, or 
> if its just very high query volume.  Maybe you could try setting 
> log_min_duration_statement to try to track down the slowest of the 
> queries.  Then post the slow queries with an explain analyze to the list.
>  
> Here is some info on setting up logging:
> http://www.postgresql.org/docs/8.1/interactive/runtime-config-logging.html
>  
> Are your queries standard SQL or do you call functions you wrote in 
> PL/pgSQl or PL/Python or anything?
>  
>  
It might be a combo of queries and load. My queries use almost 
exclusively functions, but on an unloaded dev machine performs its 
queries in aprox 10ms. When is it appropriate to start clustering 
database servers?

view thread (23+ messages)  latest in thread

Message-ID: <44F5A559.9050701@studentvillage.co.za>
Permalink:  ../44F5A559.9050701@studentvillage.co.za/
Also on:    postgresql.org/message-id/44F5A559.9050701@studentvillage.co.za

copy link · copy postgr.es

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: willo@studentvillage.co.za, dave@tridecap.com
  Subject: Re: PostgreSQL performance issues
  In-Reply-To: <44F5A559.9050701@studentvillage.co.za>

* 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