From: Tom Lane <tgl@sss.pgh.pa.us>
To: John A Meinel <john@arbash-meinel.com>
Cc: Joel Fradkin <jfradkin@wazagua.com>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Joel's Performance Issues WAS : Opteron vs Xeon
Date: Thu, 21 Apr 2005 00:35:32 -0400
Message-ID: <11216.1114058132@sss.pgh.pa.us> (raw)
In-Reply-To: <4266F7B3.7050004@arbash-meinel.com>
References: <001901c54608$b70ccfc0$797ba8c0@jfradkin>
<4266F7B3.7050004@arbash-meinel.com>
John A Meinel <john@arbash-meinel.com> writes:
> Joel Fradkin wrote:
>> Postgres was on the second run
>> Total query runtime: 17109 ms.
>> Data retrieval runtime: 72188 ms.
>> 331640 rows retrieved.
> How were you measuring "data retrieval time"?
I suspect he's using pgadmin. We've seen reports before suggesting that
pgadmin can be amazingly slow, eg here
http://archives.postgresql.org/pgsql-performance/2004-10/msg00427.php
where the *actual* data retrieval time as shown by EXPLAIN ANALYZE
was under three seconds, but pgadmin claimed the query runtime was 22
sec and data retrieval runtime was 72 sec.
I wouldn't be too surprised if that time was being spent formatting
the data into a table for display inside pgadmin. It is a GUI after
all, not a tool for pushing vast volumes of data around.
It'd be interesting to check the runtimes for the same query with
LIMIT 3000, ie, see if a tenth as much data takes a tenth as much
processing time or not. The backend code should be pretty darn
linear in this regard, but maybe pgadmin isn't.
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, john@arbash-meinel.com, jfradkin@wazagua.com
Subject: Re: Joel's Performance Issues WAS : Opteron vs Xeon
In-Reply-To: <11216.1114058132@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