![]() ![]() ![]() |
|
heapsort: Ah, the intermittent 40 second wait problem. I remember it well, although I haven't seen it in a long time despite still being on the In Home cable network.
I started a Geekzone thread on this issue more than a year ago, here it is - http://www.geekzone.co.nz/forums.asp?forumId=44&topicId=105805
mercutio:heapsort: Ah, the intermittent 40 second wait problem. I remember it well, although I haven't seen it in a long time despite still being on the In Home cable network.
I started a Geekzone thread on this issue more than a year ago, here it is - http://www.geekzone.co.nz/forums.asp?forumId=44&topicId=105805
akamai's doing nothing wrong in this situation, it's probably that it's just appearing on varying ip's, which are different when you do the lookup to when the cache does the lookup.
in some ways, the cache shouldn't do it's own dns lookup, and should just go to the destination you inititally connected to - but that'd open itself up to cache poison attacks.
i wonder if the same problem is going to manifest with google now? as i see google bounce between sydney, new zealand, and more distant quite frequently (i think it's taiwan? not sure.. )
doing a few quick reloads may force it to bypass proxy.
heapsort:mercutio:heapsort: Ah, the intermittent 40 second wait problem. I remember it well, although I haven't seen it in a long time despite still being on the In Home cable network.
I started a Geekzone thread on this issue more than a year ago, here it is - http://www.geekzone.co.nz/forums.asp?forumId=44&topicId=105805
akamai's doing nothing wrong in this situation, it's probably that it's just appearing on varying ip's, which are different when you do the lookup to when the cache does the lookup.
in some ways, the cache shouldn't do it's own dns lookup, and should just go to the destination you inititally connected to - but that'd open itself up to cache poison attacks.
i wonder if the same problem is going to manifest with google now? as i see google bounce between sydney, new zealand, and more distant quite frequently (i think it's taiwan? not sure.. )
doing a few quick reloads may force it to bypass proxy.
Didn't mean to imply that I thought it was something caused by Akamai, if that's the way you interpreted it. Just that I only ever noticed the 40 second delay fetching static data from sites that used Akamai.
Why the long delay would always be very close to 40 seconds, I don't know.
timmmay: Using only TC DNS servers the problem still happens. I'll try to narrow it down some time, the speed tracer tool isn't working well for me today.
timmmay: This has been going on for days now. Can anyone from Vodafone/TC help get this sorted? Can anyone else reproduce it?
I have to turn on my VPN to browser stuff. Pages don't load within my patience threshold which seems to be around 15 seconds.
|
![]() ![]() ![]() |