How We Test Hardware Routers

Photo of author

Tim Higgins

Updated August 2003

We use Ixia‘s free Qcheck utility to put routers through their paces. We use the simple test setup pictured below to run three basic tests.

Router Test setup diagram

1) Transfer Rate – More commonly known as Throughput, this test is a measure of how fast data flows through the router. The test sends a file from computer to computer, measures how much time it takes, and calculates the result in Mbps (Megabits per second).

Our test sends one MegaByte of data (the most that Qcheck will do). Higher numbers are better, but any result over 1-2Mbps will be plenty fast for most broadband connections, which usually run at an average of 0.5 to 0.8Mbps (even though the speed is usually advertised as being 1Mbps or higher).

2) Response Time – This test measures the delay (also known as lag, or latency) that the router introduces into a data stream, and is essentially what you’d measure by using the ping command. This test sends a small packet of data from one computer to another and measures the time it takes to receive a reply.

Our test setup runs the test 10 times in a row and calculates the average and maximum times. Lower numbers are better, especially for gaming and any voice or video applications, but anything under 10ms (milliseconds) is fine, again, because the delay that your Internet connection introduces is probably greater.

3) UDP Stream – This test measures how well a router can keep up with a continuous stream of data. In addition to giving an indication of whether you’ll have trouble listening to Internet audio or watching video program streams, it tends to show flaws in the router’s routing “engine”. It uses the connectionless UDP protocol, which has less overhead and error recovery mechanisms than the TCP protocol (picture a fire hose being turned on vs. a water bucket brigade).

Our test setup pushes data at a 500kbps (0.5Mbps) rate for 10 seconds and results in two numbers. You want the Actual Throughput number to be as close to 500kbps as possible and the Lost Data to be ideally zero, which most routers will come pretty close to. Avoid products that can’t complete the test because they lock up or that have less than 400kbps throughput or error rates above 10%.

All three tests are run from WAN to LAN (“downstream”), and repeated from LAN to WAN (“upstream”). Early routers sometimes had poorer LAN to WAN performance, but most current products have only minor variation in performance between the two directions.

We tend to use the same computers to run the tests, with all running Win98SE or WinXP, and having 300MHz or better processor speeds and memory configurations in excess of 256MB. The test machines have no other applications running during testing.

Related posts

Slow HomePlug? Try A Powerline Filter

Updated - A quick test of powerline filters shows they can help combat throughput-robbing noise.

Measuring Network Performance – NetMeter

With all the component and configuration options for constructing and managing a small network, it is important to numerically evaluate network performance. Performance measurements provide facts and statistics about the amount of data on your network and identify opportunities for improvement. Without measuring performance, the only indications of functionality are simple up and down states, as well as subjective statements based on user experience.

Packet Captures and Network Devices

Using packet papture software like Wireshark is a useful troubleshooting technique that can be used to examine packets and gather details to help find the root of a problem. In my previous post, I talked a little bit about how to use Wireshark and walked through some steps to run a simple packet capture from a PC. This time, I'm going to go a bit deeper into the how to for doing packet captures.