<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Sure,<br>
I'm hoping they put some local stuff in. But that doesn't help much.<br>
<br>
GeoIP doesn't help resolving CDN caches because it doesn't know where
the CDN caches are or what content they have.<br>
<br>
eg. many of us have Akamai servers on-net - how does GeoIP know which
customers to send where? Even we don't understand the rhyme or reason
of how Akamai does it.<br>
<br>
We're not talking a few megabits here, we're talking multiple gigabits
of content. We're talking large amounts of money to cope with
receiving that off net on the other side of the world.<br>
<br>
Again, we're just casualties of a war going on elsewhere in the
world. At best here this is a broadside aimed at people like Telstra
who don't peer locally with Google and are playing funny games with
their Bigpond resolvers ...<br>
<br>
MMC<br>
<br>
Scott Howard wrote:
<blockquote
cite="mid:f1dedf9c0912031458l42e0a9dcifce76c0e14145a5@mail.gmail.com"
type="cite">On Thu, Dec 3, 2009 at 2:40 PM, Matthew Moyle-Croft <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:mmc@internode.com.au">mmc@internode.com.au</a>></span>
wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">I think it's a great idea if
you're North America centric.<br>
<br>
But, it'll add 150ms or more to most customers and it'll hurt the
locality based services already in Australia. So, performance in
Australia will suck. eg. Akamai becomes 300ms+ vs 25-50ms depending
on where you are. Think how much traffic that means bringing in from
O/S?<br>
</div>
</blockquote>
<div><br>
It's anycast, and it would seem logical that they will roll it out to
more datacenters over time.<br>
<br>
>From both the US and Europe I'm seeing a maximum of about 20ms to get
to the nearest 8.8.8.8 server, and less than 50ms from much of Asia, so
it's neither centralised, nor North American centric. Australia seems
to be an ugly cousin at the moment...<br>
<br>
Presuming the IP addresses they are using to originate the requests
back out are correctly listed in the various GeoIP databases then the
likes of Akamai shouldn't suffer at all.<br>
<br>
>From Frankfurt :<br>
64 bytes from <a moz-do-not-send="true" href="http://8.8.8.8">8.8.8.8</a>:
icmp_seq=0 ttl=249 time=5.440 ms<br>
<br>
>From London :<br>
64 bytes from <a moz-do-not-send="true" href="http://8.8.8.8">8.8.8.8</a>:
icmp_seq=0 ttl=249 time=13.734 ms<br>
<br>
>From Washington DC : <br>
64 bytes from <a moz-do-not-send="true" href="http://8.8.8.8">8.8.8.8</a>:
icmp_seq=0 ttl=249 time=5.487 ms<br>
<br>
>From Singaopre :<br>
64 bytes from <a moz-do-not-send="true" href="http://8.8.8.8">8.8.8.8</a>:
icmp_seq=0 ttl=246 time=51.271 ms<br>
(Hits Google IP space in Singapore, but the actual resolution is
elsewhere)<br>
<br>
>From Tokyo : <br>
64 bytes from <a moz-do-not-send="true" href="http://8.8.8.8">8.8.8.8</a>:
icmp_seq=0 ttl=246 time=39.430 ms<br>
<br>
>From Adelaide :<br>
64 bytes from <a moz-do-not-send="true" href="http://8.8.8.8">8.8.8.8</a>:
icmp_seq=0 ttl=244 time=164.262 ms<br>
(Hits Google IP space in Sydney)<br>
<br>
<br>
Scott<br>
<br>
</div>
</div>
</blockquote>
</body>
</html>