Confused by 'timing' results - Mailing list pgsql-admin

From A J
Subject Confused by 'timing' results
Date
Msg-id 788866.21140.qm@web120020.mail.ne1.yahoo.com
Whole thread Raw
Responses Re: Confused by 'timing' results  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-admin
time echo '\timing \\select * from  table1 where id = 123;' | psql

I am trying to time a simple select statement from different clients located at different places. The database is on US east-coast.
In the above query. the 'timing' will time the database time and the 'time' command at the very start will time the complete time for the query including network time.

When I run the query on the database, I get:
Time: 2.357 ms
real    0m0.010s

From a separate client on east-coast:
Time: 29.555 ms
real    0m0.164s

From a separate client on the west-coast:
Time: 82.236 ms
real    0m0.408s

From a separate cloud client from asia:
Time: 262.715 ms
real    0m1.311s

While I did expect the 'real' time to be different and increase (from server to east-coast to west-coast to asia ), I did not expect the database time to increase appreciably. Can anyone explain why the database time for a simple select (reading from buffer) would increase so much (from 2.357 to 29.555 to 82.236 to 262.715ms) because of the client location ?

Because I ran the select several times before the above test, am assuming all the selects just read from the shared buffer and did not hit the actual disks on the database server.


Thank you. - AJ

pgsql-admin by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: General migration question
Next
From: "Kevin Grittner"
Date:
Subject: Re: Confused by 'timing' results