Re: new latency meters and network performance foo
Posted: Thu Jun 09, 2011 11:06 am
How'd IPv6 day go, Thunder?
This was a triumph. I'm making a note here: "HUGE SUCCESS". It's hard to overstate my satisfaction.tethealla wrote:How'd IPv6 day go, Thunder?
General industry analysis has been favourable. Both xbox.com and mastercard.us have decided to both keep their quad A records active (meaning they will continue to be reachable via ipv6). Google is leaving the YouTube video stream portion of YouTube enabled (HTML and static content will be served from public v4 DNS). Blizzard are going to continue to keep the realms involved in yesterday's tests dual stacked with IPv4 and IPv6 for a while for continued testing.
Some WoW specific info that might interest you:
- General community opinion was that, if you don't have native IPv6, then Hurricane Electric's tunnel provides a 'better' experience for WoW than SIXXS. 'Better' is in quotes, since it's subjective, but it could probably be translated as faster packet routing to those realms and an easier time setting up the persistent IPv6 tunnel.
- In some instances, players have reported a better ping time/lower latency over IPv6 compared to IPv4. This is quite surprising, since there has been little work done by the major backbones to optimize global routing.
- There were some issues with the way the WoW client auto-detects an IPv6 connection on the local machine. Specifically, Mac OS client had some problems, and clients on machines with multiple network adapters where only one of the two adapters had an IPv6 address also had some problems
Personally speaking, I'm glad to see IPv6 had some great successes yesterday all over the world. I had a man on the ground at the SFBA after-event party with Google/Cisco/etc, and every entity represented reported no significant rise in influx of calls, tweets, outages etc., and the NANOG forums are full of threads saying good things today. My personal hope is that ISOC quickly turn around and sponsor a World IPv6 Week this summer so that more data can be gathered for deeper analysis on routing paths, bandwidth usage, packet sizes etc.