From: | "Lou O'Quin" <loquin(at)talleyds(dot)com> |
---|---|
To: | <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Query performance |
Date: | 2005-03-11 19:38:16 |
Message-ID: | s2319147.076@mesagate.talleyds.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi Tom. I referenced the status line of pgAdmin. Per the pgAdmin help file:
"The status line will show how long the last query took to complete. If a dataset was returned, not only the elapsed time for server execution is displayed, but also the time to retrieve the data from the server to the Data Output page."
Lou
>>> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 3/11/2005 12:10 PM >>>
"Lou O'Quin" <loquin(at)talleyds(dot)com> writes:
> it appears to actually be hypersensitive to the transport delay. The =
> ratios of time for the data transport (assuming 1 for the local server) =
> are:
> 1 : 2.43 : 7.71
> whereas the query execution time ratios are:
> 1 : 2.08 : 25.5 (!!!)
How do you know that's what the data transport time is --- ie, how can
you measure that separately from the total query time?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Arshavir Grigorian | 2005-03-11 19:48:02 | Postgres on RAID5 |
Previous Message | Tom Lane | 2005-03-11 19:10:27 | Re: Query performance |