Re: Confused by 'timing' results

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>,"A J" <s5aly(at)yahoo(dot)com>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Confused by 'timing' results
Date: 2010-09-02 19:09:39
Message-ID: 4C7FB02302000025000350AC@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

A J <s5aly(at)yahoo(dot)com> wrote:

> With this approach, I will be assuming that the query time does
> not change due to client location, which though reasonable, is
> still an assumption.

As I explained in an earlier post, the query can block on the server
due to network bandwidth or latency. So the "wall time" for query
execution can indeed be different based on location, especially if
you are returning a large result set. But why would you want to
separate out this type of network delay from the others?

If you want to eliminate it as a factor, you need some tier to
receive requests and queue them, pull them from the queue and run
them with another queue for results, and send the results from the
queue back to the requester. This is what we do, BTW, and it does
give us the ability to totally isolate run time from network
influences.

-Kevin

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Marlowe 2010-09-02 19:15:35 Re: Confused by 'timing' results
Previous Message A J 2010-09-02 19:07:55 Re: Confused by 'timing' results