Over the course of 2015, I noticed a trend. Rather than replacing routers when they literally stopped working, I increasingly needed to act earlier—swapping in new gear because an old router could no longer keep up with increasing Internet speeds available in the area. Famously around the Ars forums, this problem soon evolved into our homebrew router initiative. In January, I showed my math as a DIY-Linux router outpaced popular off-the-shelf options like the Netgear Nighthawk X6 and the Linksys N600 EA-2750. And in August, I shared the steps necessary to build one of your own.
After readers got a look at the performance charts, I got a ton of outraged "why didn't you test my favorite brand?!" comments. If you were one of those skeptics, congrats—today is your day! The Ars homebrew router special has been coaxed out of retirement to test its speeds against an entirely new lineup of gear. And to raise the stakes a bit further, the Ars team has broken out some new and improved methods that test more hardware and a couple of purpose-designed router distros. This time, we're even offering power consumption figures as well.

On the right: our test server Monolith, newly upgraded with an Intel server-grade gigabit NIC, plus a trusty Kill-A-Watt power meter. (credit: Jim Salter)
Methodology updates
For our new and improved testing, we're still hammering everything with streams of HTTP connections and varying filesizes. But we've tightened down the time that the HTTP sockets are allowed to respond (from 240 seconds down to 20) mostly in order to make prettier graphs. Wait, did I say graphs? (Yes!) This time around, we're going to look at real time bandwidth graphs of the testing as it's being performed, which lets us see what's happening with the contestants more clearly than we could the first time around. We'll also look at power consumption for each device, both idle and under (routing) load. And when we look at raw throughput numbers, we're going to look solely at completed downloads, since we care more about "how much can we successfully download" rather than "how much useless noise this thing can make on my network."