From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
To: ryan groth <postgres@cpusoftware.com>
Cc: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: Steinar H. Gunderson <sgunderson@bigfoot.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Joins and full index scans...mysql vs postgres?
Date: Thu, 23 Feb 2006 10:52:11 +0800
Message-ID: <43FD235B.7000207@familyhealth.com.au> (raw)
In-Reply-To: <E1FBz6X-0007Do-9z@zeus.liquidweb.com>
References: <E1FBz6X-0007Do-9z@zeus.liquidweb.com>
The pgAdmin query tool is known to give an answer about 5x the real
answer - don't believe it!
ryan groth wrote:
> Hmm, it came from the timer on the pgadmin III sql query tool. I guess
> the 1,000ms includes the round-trip? See the wierd thing is that
> mysqlserver is running default configuration on a virtual machine
> (P3/1.3GHZ conf'd for 128mb ram) over a 100m/b ethernet connection.
> Postgres is running on a real P4/3.0ghz 4GB running localhost. Timings
> from the mysql query tool indicate that the 6.5k record query runs in
> "1.3346s (.3361s)" vs. the pgadmin query tool saying that the query runs
> "997+3522 ms". Am I reading these numbers wrong? Are these numbers
> reflective of application performance? Is there an optimization I am
> missing?
>
> Ryan
>
>
>> On Wed, 22 Feb 2006, ryan groth wrote:
>>
>>> Does this work:
>>>
>>> "Merge Left Join (cost=0.00..2656.36 rows=6528 width=1522) (actual
>>> time=0.057..123.659 rows=6528 loops=1)"
>>> " Merge Cond: ("outer".uid = "inner".uid)"
>>> " -> Merge Left Join (cost=0.00..1693.09 rows=6528 width=1264)
>>> (actual time=0.030..58.876 rows=6528 loops=1)"
>>> " Merge Cond: ("outer".uid = "inner".user_id)"
>>> " -> Index Scan using users_pkey on users (cost=0.00..763.81
>>> rows=6528 width=100) (actual time=0.016..9.446 rows=6528 loops=1)"
>>> " -> Index Scan using phorum_users_base_pkey on
>>> phorum_users_base (cost=0.00..822.92 rows=9902 width=1168) (actual
>>> time=0.007..15.674 rows=9845 loops=1)"
>>> " -> Index Scan using useraux_pkey on useraux (cost=0.00..846.40
>>> rows=7582 width=262) (actual time=0.007..11.935 rows=7529 loops=1)"
>>> "Total runtime: 127.442 ms"
>> Well, this implies the query took about 127 ms on the server side. Where
>> did the 1000 ms number come from (was that on a client, and if so, what
>> type)?
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 6: explain analyze is your friend
>>
>>
>
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: chriskl@familyhealth.com.au, postgres@cpusoftware.com, sszabo@megazone.bigpanda.com, sgunderson@bigfoot.com
Subject: Re: Joins and full index scans...mysql vs postgres?
In-Reply-To: <43FD235B.7000207@familyhealth.com.au>
References: <E1FBz6X-0007Do-9z@zeus.liquidweb.com> <43FD235B.7000207@familyhealth.com.au>
* 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