And -
Pinging appspot.l.google.com [66.102.11.141] with 32 bytes of data:
Reply from 66.102.11.141: bytes=32 time=36ms TTL=52
Reply from 66.102.11.141: bytes=32 time=36ms TTL=52
Reply from 66.102.11.141: bytes=32 time=36ms TTL=52
Reply from 66.102.11.141: bytes=32 time=36ms TTL=52
Ping
Ok, well I'm now seeing much *worse* (~600ms) latency in Sydney -
reliably slower since the maintenance last night.
ping performance.latest.pet-software.appspot.com
PING appspot.l.google.com (66.102.11.141): 56 data bytes
64 bytes from 66.102.11.141: icmp_seq=0 ttl=54 time=18.807 ms
64 bytes
Prague CZ, O2 ADSL
Ajax request latency of 268ms
(this is when I hit the 'Go' button again - the first one was ~700ms -
but the page's HTML was actually loading at that time I think)
On Aug 17, 4:16 am, gjs garyjamessi...@gmail.com wrote:
Home Ajax request latency of 425ms
Page One Ajax
Location: Los Altos, CA (10 mins from google-hq)
average latency: 170ms
If you are planning on collating/summarizing all this info, i'd
appreciate it if you
could send out a link to the summary.
- S.. Sriram
On Aug 13, 3:44 am, Martyn martyn.cutc...@googlemail.com wrote:
Hi there,
I am
77ms to 127ms
Rutgers University, New Jersey, US
On Aug 18, 2:42 pm, molicule molic...@gmail.com wrote:
Location: Los Altos, CA (10 mins from google-hq)
average latency: 170ms
If you are planning on collating/summarizing all this info, i'd
appreciate it if you
could send out a link to the
Plugged in to DSL I get ~150ms.
Ben
On Aug 14, 10:13 am, Martyn martyn.cutc...@googlemail.com wrote:
Hi Ben,
Clearly all parts of the network add latency. The bit that adds the
most is the most significant - wherever it may be. The claimed
AppEngine latency in the status figures (for
Queenstown New Zealand: 440-490ms.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send
Home Ajax request latency of 425ms
Page One Ajax request latency of 439ms
Page Two Ajax request latency of 420ms
More Ajax request latency of 836ms
After trying multiple times most responses are around 380~420ms
From Australia ( with chrome on windoze xp )
Regards
On Aug 17, 9:02 am, GregF
Orange, NSW, Aust -
low: 380ms, high: 480ms, avg: 440ms
Also moved from UK to Australia recently, and anecdotal 'sluggishness'
definately more noticeable in Aus than in the UK - Melbourne, Sydney
Orange.
On Aug 14, 10:13 am, Scott sje...@gmail.com wrote:
Melbourne, Australia:
low: 352ms,
Also from Orange, Australia -
ping performance.latest.pet-software.appspot.com
PING appspot.l.google.com (66.102.11.141): 56 data bytes
64 bytes from 66.102.11.141: icmp_seq=0 ttl=57 time=20.131 ms
64 bytes from 66.102.11.141: icmp_seq=1 ttl=57 time=24.465 ms
64 bytes from 66.102.11.141:
Location: Zagreb, Croatia
Low - 167, High - 195, Avg - ~175
Cheers,
Ivan
On Aug 13, 12:44 pm, Martyn martyn.cutc...@googlemail.com wrote:
Hi there,
I am investigating request latency for AppEngine after experiencing
significantly lower performance then reported in the Java status
results.
That's interesting!
On Aug 14, 9:41 am, hawkett hawk...@gmail.com wrote:
Also from Orange, Australia -
ping performance.latest.pet-software.appspot.com
PING appspot.l.google.com (66.102.11.141): 56 data bytes
64 bytes from 66.102.11.141: icmp_seq=0 ttl=57 time=20.131 ms
64 bytes from
I repeated Hawketts ping results for performance.latest.pet-
software.appspot.com and got similar times ~22ms.
So can anyone suggest why we experience such diverse request latency
if the underlying infrastructure is so good? - Hawkett (Australia)
reported avg 440ms with a ping of 22ms and I get
Okay, just spoke with a network expert.
He suggests that Google are any-casting the DNS. So the pet-
software ping is not really doing a round-trip to the app-server.
Where perhaps the appspot.com ping is.
--~--~-~--~~~---~--~~
You received this message because
New Orleans, LA : 170 - 185 ms
On Aug 14, 7:12 am, Martyn martyn.cutc...@googlemail.com wrote:
Okay, just spoke with a network expert.
He suggests that Google are any-casting the DNS. So the pet-
software ping is not really doing a round-trip to the app-server.
Where perhaps the
Am I stupid, or does this test depend as much or more on the last
mile and its transport as it does on the underlying network
topology? I'm in Vancouver, Canada, and I'm getting results between
300ms and 600ms, but I'm also using a cellular modem right now.
Ben
On Aug 14, 7:09 am, ajacks504
Hi Ben,
Clearly all parts of the network add latency. The bit that adds the
most is the most significant - wherever it may be. The claimed
AppEngine latency in the status figures (for Java and Python) is based
on a round-trip http request, I guess that is not necessarily a
browser test.
Buenos Aires, ~210ms no peaks
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send
US North Carolina: First request 130ms, then ~65ms - 75ms (Cable modem
here)
Diego
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to
I'll start off by reporting that:
In South-East England I am seeing typical latency reported at ~170ms,
but generally ranging between 160ms and 220ms
On Aug 13, 11:44 am, Martyn martyn.cutc...@googlemail.com wrote:
Hi there,
I am investigating request latency for AppEngine after
Near Boston: low 84ms, high 400ms, median around 95ms.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe
Amsterdam: ~150ms low: 130ms, high 240ms
On Aug 13, 3:53 pm, Joshua Smith jesm...@kaon.com wrote:
Near Boston: low 84ms, high 400ms, median around 95ms.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App
Somerset, NJ: low 80ms, high 340ms, median around 90ms.
On Aug 13, 10:53 am, Koen Bok k...@madebysofa.com wrote:
Amsterdam: ~150ms low: 130ms, high 240ms
On Aug 13, 3:53 pm, Joshua Smith jesm...@kaon.com wrote:
Near Boston: low 84ms, high 400ms, median around 95ms.
Ouch!
On Aug 13, 8:58 pm, Jarek Zgoda jarek.zg...@gmail.com wrote:
Warsaw, Poland here. Typical ~240ms, ranging from 210ms to 740ms (!).
On 13 Sie, 12:44, Martyn martyn.cutc...@googlemail.com wrote:
Hi there,
I am investigating request latency for AppEngine after experiencing
Tokyo Japan: 220ms ~ 300ms
--
Takashi Matsuo
On Thu, Aug 13, 2009 at 7:44 PM, Martynmartyn.cutc...@googlemail.com wrote:
Hi there,
I am investigating request latency for AppEngine after experiencing
significantly lower performance then reported in the Java status
results.
This
Melbourne, Australia:
low: 352ms, high 375ms, average approx 360ms
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com
To
Phnom Penh, Cambodia: typical latency is 500ms. Very consistent, 487ms
~ 536ms.
On Aug 13, 5:44 pm, Martyn martyn.cutc...@googlemail.com wrote:
Hi there,
I am investigating request latency for AppEngine after experiencing
significantly lower performance then reported in the Java status
São Paulo, Brazil - average 210ms
-- rodrigo
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this
28 matches
Mail list logo
