Re: Query 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

"Lou O'Quin" <loquin(at)talleyds(dot)com> writes:
> 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."

Well, you should probably ask the pgadmin boys exactly what they are
measuring. In any case, the Postgres server overlaps query execution
with result sending, so I don't think it's possible to get a pure
measurement of just one of those costs --- certainly not by looking at
it only from the client end.

BTW, one factor to consider is that if the test client machines weren't
all the same speed, that would have some impact on their ability to
absorb 15K records ...

regards, tom lane