pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ruben Rubio Rey <ruben@rentalia.com>
To: john_oshea@wordbank.com
Cc: pgsql-performance@postgresql.org
Subject: Re: SQL CPU time usage
Date: Thu, 18 May 2006 16:52:23 +0200
Message-ID: <446C8A27.9030100@rentalia.com> (raw)
In-Reply-To: <25265881-37A8-4CD4-952F-3E7F4CE97F4D@wordbank.com>
References: <446B3F6A.9070205@rentalia.com>
	<25265881-37A8-4CD4-952F-3E7F4CE97F4D@wordbank.com>

john_oshea@wordbank.com wrote:

> On 17 May 2006, at 16:21, Ruben Rubio Rey wrote:
>
>> I have a web page, that executes several SQLs.
>>
>> So, I would like to know witch one of those SQLs consumes more CPU.
>> For example,
>> I have SQL1 that is executed in 1.2 secs and a SQL2 that is  executed 
>> in 200 ms.
>>
>> But SQL2 is executed 25 times and SQL1 is executed 1 time, so  really 
>> SQL2 consumes more CPU time.
>>
>> Is there any way to know this?
>> I have think that logging all SQLs and then cheking it is a way to  
>> do it ... any other idea?
>
>
> Practical Query Analysis: <http://pqa.projects.postgresql.org/; does  
> exactly that (scan historic logs). Very nice indeed and more than  
> worth the money (it's BSD-licensed)
>
thanks



view thread (4+ messages)  latest in thread

Message-ID: <446C8A27.9030100@rentalia.com>
Permalink:  ../446C8A27.9030100@rentalia.com/
Also on:    postgresql.org/message-id/446C8A27.9030100@rentalia.com

 · 

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: ruben@rentalia.com, john_oshea@wordbank.com
  Subject: Re: SQL CPU time usage
  In-Reply-To: <446C8A27.9030100@rentalia.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