pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Chris Kratz <chris.kratz@vistashare.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Large time difference between explain analyze and normal run
Date: Thu, 10 Feb 2005 13:58:37 -0500
Message-ID: <28553.1108061917@sss.pgh.pa.us> (raw)
In-Reply-To: <200502101334.40341.chris.kratz@vistashare.com>
References: <200502101334.40341.chris.kratz@vistashare.com>

Chris Kratz <chris.kratz@vistashare.com> writes:
> Does anyone have any idea why there be over a 4s difference between running 
> the statement directly and using explain analyze?

>  Aggregate  (cost=9848.12..9848.12 rows=1 width=0) (actual 
> time=4841.231..4841.235 rows=1 loops=1)
>    ->  Seq Scan on answer  (cost=0.00..8561.29 rows=514729 width=0) (actual 
> time=0.011..2347.762 rows=530576 loops=1)
>  Total runtime: 4841.412 ms

EXPLAIN ANALYZE's principal overhead is two gettimeofday() kernel calls
per plan node execution, so 1061154 such calls here.  I infer that
gettimeofday takes about 4 microseconds on your hardware ... which seems
a bit slow for modern machines.  What sort of box is it?

			regards, tom lane



view thread (5+ messages)  latest in thread

Message-ID: <28553.1108061917@sss.pgh.pa.us>
Permalink:  ../28553.1108061917@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/28553.1108061917@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, chris.kratz@vistashare.com
  Subject: Re: Large time difference between explain analyze and normal run
  In-Reply-To: <28553.1108061917@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