Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Fact Finding: Riot Games Negotiates Direct Connection From Users to Servers

DZone's Guide to

Fact Finding: Riot Games Negotiates Direct Connection From Users to Servers

Mitchell Zelmanovich analyzes the claim that Riot Games has been trying to better the direction connection between its users and its servers.

Free Resource

Evolve your approach to Application Performance Monitoring by adopting five best practices that are outlined and explored in this e-book, brought to you in partnership with BMC.

Every day, more than 27 million people depend on Riot Games’ League of Legends to deliver an incredibly fast user experience. My fellow Catchpointer Greg Rubin and I are two of them. Like just about everyone else who plays, we can tell when our connection to the server is faster or slower, even by a handful of milliseconds. A faster connection means better input times, and the ability to react faster to game situations. We noticed recently that we were doing better than usual, and saw that our ping times were improving.

Since we’re in the industry, we follow Riot’s technical blog, which claimed that the company was frustrated with its lack of control over third-party routing and had been actively working to provide direct routes between players and their servers. Naturally, we wanted to verify this. Here’s what we saw.

First, we set up traceroute tests on Catchpoint last-mile nodes, from Verizon (which I use), and Time Warner (which Greg uses). You can see in the chart below that Verizon (ASN 701) connects directly to Riot Games (ASN 6507)—just as they said.

League of Legends 1

In this next chart, you can see that connecting through Time Warner (ASN12271) also connects directly to Riot Games (ASN 6507). Although Greg’s experience is still a hair slower than mine, which is awesome.

LoLNext, we set up traceroute tests from the same nodes to another gaming server, from Blizzard—Heroes of the Storm, which is similar to League of Legends. As you can see in the next chart, Greg’s route to the server (hosted on AT&T’s network) was more complicated, adding an additional provider, XO Communications. Mine went direct to AT&T and, again, connected faster than Greg’s.

Riot Games provider

The bottom line is that Riot Games’ claim is true. They found a way to shave milliseconds off response times by working around internet service providers and negotiating their own peering on a network-by-network basis. This is a great example of a company understanding that its online experience is critical and taking matters into their own hands to deliver an amazing user experience. And believe me, users can tell the difference.

Evolve your approach to Application Performance Monitoring by adopting five best practices that are outlined and explored in this e-book, brought to you in partnership with BMC.

Topics:
performance ,traceroute ,riot games ,networks

Published at DZone with permission of Mitchell Zelmanovich, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}