From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: Ang Chin Han <angch@bytecraft.com.my>
Cc: Rhaoni Chiu Pereira <rhaoni@sistemica.info>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: Query too slow
Date: Tue, 26 Aug 2003 12:01:32 -0400
Message-ID: <27125.1061913692@sss.pgh.pa.us> (raw)
In-Reply-To: <20030826084326.M30963-100000@megazone.bigpanda.com>
References: <20030826084326.M30963-100000@megazone.bigpanda.com>
Stephan Szabo <sszabo@megazone.bigpanda.com> writes:
> On Tue, 26 Aug 2003, Ang Chin Han wrote:
>> Veering aside a bit, since we usually pinpoint performance problems by
>> looking at EXPLAIN ANALYZE's differences between the planner's
>> estimation and actual execution's stats, what's involved in parsing the
>> EXPLAIN ANALYZE results, and highlighting the places where they are way
>> different? Bold, underline, or put some asterisks in front of those steps.
> The hardest part is determining where it matters I think. You can use the
> row counts as the base for that, but going from 1 row to 50 is not
> necessarily going to be an issue, but it might be if a nested loop is
> chosen.
We've been chatting about this idea among the Red Hat group. The RHDB
Visual Explain tool (get it at http://sources.redhat.com/rhdb/) already
computes the percent of total runtime represented by each plan node.
It seems like we could highlight nodes based on a large difference
between estimated and actual percentage, or just highlight the nodes
that are more than X percent of the runtime.
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, sszabo@megazone.bigpanda.com, angch@bytecraft.com.my, rhaoni@sistemica.info
Subject: Re: Query too slow
In-Reply-To: <27125.1061913692@sss.pgh.pa.us>
References: <20030826084326.M30963-100000@megazone.bigpanda.com> <27125.1061913692@sss.pgh.pa.us>
* 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