Skip to main content

Steam Pushes Over 3/4 of a Terabit on Their CDN

The Steam Summer Sale is upon us once again. I, like many Steam users, look forward to these seasonal events. Unlike most Steam users though (I assume), I have a constant fascination with the Steam Content Server Stats page. I like watching the trends and seeing just how much bandwidth the Steam CDN can eat up, keeping a mental note of the highest peak utilization.

In terms of the trend, utilization is often around 200 - 300 Gbps, sometimes dipping below 200 when there’s nothing particularly exciting happening (e.g. a not-so-great midweek sale). Prior to the sale, the highest I had ever seen the peak value was 658 Gbps. The sales are often the record breakers and this summer did not disappoint. Below is a screen capture showing a peak of over 768 Gbps, 3/4th’s of a terabit.


Even the smaller of those numbers is nothing to sneeze at. That’s a lot of bandwidth. In late 2010 when Netflix announced a move to Level 3 for streaming of their video services, Level 3 stated that they had 1.65 terabits of global CDN bandwidth with plans to add 2.9 Tbps more. Now, that’s not just the bandwidth allocated to Netflix but Level 3’s entire global CDN which serves various other customers. Granted we all pretty much know Steam is not small in terms of users, but this just further shows that they are definitely playing with the big boys here. (Today, Level 3 boasts a total 5.6 Tbps of global capacity, with today’s numbers Steam could still eat a huge chunk of that if they used Level 3 exclusively).


I was initially thinking about holding off writing this post up as there is a good possibility for Steam’s current throughput record to be broken as we are just starting the summer sale. However, I don’t think it can be beat by much.  Looking at the individual server loads, you can see many of them are being pushed to the max. While the demand could very well be capable of using up over a terabit, it doesn’t look like Steam could provide it without adding more servers. The images below show the demand that the Summer Sale has brought on the network.

I’d personally love to read up on some details of Steam’s CDN, something like a High Scalability post. It’s not clear to what extent (if any) Valve runs their own content servers or utilizes other company CDN/cloud services.  I did find information on Valve using Highwinds’ CDN for some of their Steam traffic. The majority of Steam traffic may even utilize Highwinds, though the article is not specific. I’m somewhat surprised at this since CDN pricing is usually seen as a bit high, so they must be getting a good volume discount. I remember once tracking an IP that my Steam client was connected on to Limelight Networks, so multiple cloud providers are probably at work here. If so, why the hard limit on individual servers (whatever those may be)? Why slow download speeds during sales? Could Steam actually be placing that much load on multiple cloud providers? Perhaps, but those providers are not likely to let their other customers be drastically affected due to the demand of one other customer.  My guess is that there is some sort of throttling going on as part of the negotiations. But whatever it may be, Valve certainly knows what they’re doing.

Comments

Dustin said…
Great article on Steam and Highwinds CDN! We are very happy working with them. Email me if you have any questions.

Dustin DeTorres
Social Media Manager @highwinds

Popular posts from this blog

Quick Deepstream.io Setup Using JSPM

Cross post from my employer's development blog: http://rootinc.github.io/2016/02/12/deepstream-jspm/
Want to use JSPM rather than Bower for running the Deepstream.io example? Follow these steps. This is basically a duplicate of the [Getting Started tutorial][tutorial] on the [Deepstream.io website][website] but using a really simple JSPM setup. This is a very crude guide where I list everything I had to do to get things running.

Create an empty project folder npm install deepstream.io Copy server code verbatim from the Getting Started guide jspm install npm:deepstream.io-client-js Hit enter for all the prompts from JSPM

We’re going to modify the client side code a little bit. We have native support for ES6 compiling with JSPM/Babel so we can import the Deepstream client directly:

import deepstream from 'deepstream.io-client-js'; let ds = deepstream( 'localhost:6020' ).login();

let record = ds.record.getRecord( 'someUser' );

let input = document.querySelector( 'inp…

Atari E3 2004 PAL digital press kit

Making note of some old swag. The Atari E3 2004 PAL digital press kit. See video for details.






Fancy FTP Deployment with Grunt

I recently dove into Grunt.js at work for automating our build process and I haven’t looked back. It’s an awesome tool with a plug-in for just about anything. I expected the usual would be there like JavaScript minification and concatenation, but I was surprised at a few others that I found, one being for FTP file deployment. Just shows how popular and community supported Grunt is.

There are a few FTP plug-ins available for Grunt. I didn’t do an analysis of all of them but ran across grunt-ftp-push which seemed to do what I needed so I decided to try it out. A simple ftp-push setup to upload an entire project via FTP could look like this:

grunt.initConfig({ftp_push:{all:{options:{host:'example.com',port:21,dest:'/project/path/',username:'user',password:'pass'},expand:true,cwd:'dist',src:['**/*','!**/*.zip']}}});
Some details here: I opted to put the username and password in the main config rather than using an .ftpauth file. The …