> On 23 May 2016, at 22:44, Fred Baker (fred) <[email protected]> wrote: > >> On May 23, 2016, at 8:16 AM, Lorenzo Colitti <[email protected]> wrote: >> >> Very nice. I wonder why www.facebook.com shows much better IPv4 latency? > > First guess is something about data center location. IPv6 works well for them > on the UA west coast and measurement points in Australia and SE Asia, but IPv4 > is better in Europe and the US east coast. Now look at LinkedIn.
Let me stress this again. This is a toy! Not only because the web interface is crappy, but also because the dataset is miniscule. Although the dataset has a very good coverage of dual-stacked vantage points, the sample size is very small (1 sample / probe). This provides a very small peak into the performance of a website. As you know, I have been doing long-term v6 performance measurements from (although a smaller set of) 80 SamKnows probes. The 3-year long trend shows that performance towards www.facebook.com has dramatically improved over time. Using this sample (as of today), I don’t see www.facebook.com to be slower over IPv6. I created this toy to show that RIPE Atlas can be used to provide such a service. I decided to showcase to you because I wanted to learn if there is interest in having such a service. With the amount of positive feedback I have received in a single day, I’ll be happy to spend cycles to run this measurement for a longer duration. This will require also blessing from the RIPE NCC because the project will cross all sorts of rate thresholds :-) With permission from RIPE NCC, let me run this every hour from all probes for at least a week and then we should look at the results. At this point, just play with it, but please don’t use it to declare any website faster or slower. Best, Vaibhav >> On Mon, May 23, 2016 at 11:30 PM, Bajpai, Vaibhav >> <[email protected]> wrote: >> Dear v6-ops, >> >> Here [a] is a toy v6 service I came up with during the RIPE >> Atlas hackathon over this weekend. Thought I share this along: >> >> [a] http://goo.gl/hbzbwD >> >> You enter a dual-stacked website (ALEXA top 10K) and it shows >> you the difference in TCP connect times over v4 and v6 as seen >> by all dual-stacked RIPE Atlas probes (~1.3K probes). You can >> also filter the visualisation from a specific origin-AS. This >> additional filter can be useful to view performance towards a >> website from a specific origin-AS (say 3320). >> >> Disclaimer: This is an outcome of a 1.5d long hackathon project. >> As such, the codebase is possibly inundated with bugs. Please >> don’t see it as a production service :-) >> >> Feedback most welcome! >> >> Best, Vaibhav =================================== Vaibhav Bajpai www.vaibhavbajpai.com Room 91, Research I School of Engineering and Sciences Jacobs University Bremen, Germany ===================================
