Netgear 2.4GHz Ideal Performance

Starting with our 2x2:2 2.4GHz Netgear WNR3500L router, testing as expected was particularly variable on the 2.4GHz spectrum. For this test, the router was set up in an upstairs room of my house with no Internet connectivity. The laptops were tested individually (except for the latency test, where a second laptop was also powered on—we used the Bigfoot 1102 equipped laptop, though informal testing suggests the choice of second laptop was irrelevant), at a distance of around five feet from the router.

I adjusted the position and orientation of the laptops during testing in order to achieve what appears to be a best-case result. The connection speeds achieved are as follows: Atheros, 300Mbps; Bigfoot, 300Mbps; Intel 1030, 144Mbps; Intel 6230, 144Mbps; Intel 6300, 300Mbps; Realtek, 144Mbps. You’ll notice that several of the cards were not able to connect at their maximum theoretical speed, specifically the Intel 6230 had issues here on both laptops with that controller, and the Realtek and Intel 1030 connect at 144Mbps instead of 150Mbps. The 6300 does obtain a 300Mbps connection, which is the maximum supported by the Netgear router, and the Bigfoot and Atheros cards also link at 300Mbps. Part of the issue here is the use of 40MHz channels, which are often difficult to maintain in the real world. When the wireless driver (and/or router) detect enough interference to switch to 20MHz channels, you lose a lot of potential bandwidth. Despite numerous reboots and other tweaking, we never could get some of the devices to maintain a 300Mbps connection. With that out of the way, here are the results.

Windows File Copy - Netgear WNR3500L Ideal

Windows File Copy - Netgear WNR3500L Ideal

NTttcp Throughput - Netgear WNR3500L Ideal

NTttcp Throughput - Netgear WNR3500L Ideal

Netperf Throughput - Netgear WNR3500L Ideal

Netperf Throughput - Netgear WNR3500L Ideal

GaNE Latency - Netgear WNR3500L Ideal

GaNE Latency - Netgear WNR3500L Ideal

Straight out of the gate, we see a separation develop among the various contenders. At the top of nearly every chart sits the Bigfoot Killer 1102; if it doesn’t outright win, it at least places so close as to be nearly a tie. Keep in mind again that wireless performance is prone to variance, so anything within 5% is close enough that you don’t need to worry much. As noted above, the 6230 would only link up at 144Mbps, which definitely hurts raw throughput; even so, the ASUS K53E appears to work better overall than the Clevo W150HM unit does, showing that not all laptop antennae are equal.

There are two specific tests where the Bigfoot 1102 walks away with the performance crown. The first test is latency, with the 1102 coming very close to wired Ethernet levels of latency (we’ll show those later). The next closest contender for latency is the Realtek solution, and you likely wouldn’t notice the difference. The catch is that there are other areas where the 1102 beats the Realtek quite handily, but we’re getting ahead of ourselves. Outside of the Realtek 8188CE, the Bigfoot 1102’s worst performance is better than the best results from all of the other solutions.

During GaNE testing, virtually every other wireless solution shows occasional spikes of anywhere from 20 to 100+ ms, usually lasting for 5-10 seconds. The Bigfoot 1102 actually showed the same issue, but when we used the Killer Network Manager and set the priority of GaNE to 1 (highest), latency dropped to what we’re reporting above. What’s causing these spikes? It might be Windows searching for other wireless networks; we’re not sure. However, we do have an interesting real-world test that corroborates the GaNE latency results.

If you look at the NTttcp maximum throughput tests, several of the 300Mbps devices are close together. The Atheros AR8132, Bigfoot 1102, and Intel 6300 are all about twice as fast as the other wireless devices. Look at the single large file copy throughput and those same three controllers rise to the top. What’s interesting is what happens when we start copying a lot of smaller files. Suddenly it’s not a question of throughput but is instead how quickly the copy process can transfer each file. Watching the real-time throughput in the networking tab of Windows Task Manager (add the “Bytes Sent/Received per Interval” columns to see this), the lowest throughput on the 1102 is at least double and often triple what the other controllers manage. When you’re copying files and directories, Windows opens a network stream, starts receiving data, and then closes the stream for each file (there might be some other steps, but that description will suffice). If each of those steps ends up taking a few extra milliseconds, multiply that by 9000 and suddenly the process ends up going a lot slower when you have poor latency. In fact, given we’re only transferring 440MiB of data, it appears that the latency/handshaking process takes up around 60 seconds on the Bigfoot 1102 and over 140 seconds on the next closest competitor. Ultimately, GaNE does appear to correlate well with real-world testing.

So do we have a winner in the Bigfoot 1102? If you happen to have a 2x2:2 2.4GHz router (which is probably the most common 802.11n router type) in the same room, the answer is a definite yes. A couple other solutions can come close in terms of pure bandwidth, but the combination of low latency, consistency of connection, and stability offered by the Killer 1102 can’t be beat. Anyone running one of the controllers that only support a single spatial stream (e.g. the Intel 1030 and Realtek 8188CE) will obviously not come close to the same level of performance as the Bigfoot 1102. If you’re after better wireless performance, getting a Killer Wireless-N in your laptop appears to be a good step…but what happens when we move into a different room and obstruct the signal?

Testing Overview Netgear 2.4GHz Obstructed Performance
Comments Locked

52 Comments

View All Comments

  • neothe0ne - Sunday, August 14, 2011 - link

    "And Dell, Asus, Acer, and Sony all do the same thing."

    Are you sure about that? I was under the impression HP and Lenovo were alone in the industry with the WLAN whitelist. And anyway, Dell does offer the Intel Centrino 6230 on the XPS 15 now, unlike HP's dv6 which is stuck in budget-tier Intel WiFi Link 1000 land.
  • cjl - Tuesday, August 16, 2011 - link

    Dell, at least in their Alienware products, definitely does not whitelist. After reading this article, I got one of the Killer 1102 cards for my M11xR2 (which comes with a rather terrible card by default, and there were no upgrade options offered), and it works just fine. I popped it in, installed the drivers, and everything has been working great since.
  • Musafir_86 - Thursday, August 11, 2011 - link

    Hello,

    -Thanks for the article, but did you tested those adapters with or without any security/encryption/password protection scheme? I mean WEP or WPA/WPA2 - I think encryption put some overhead in the throughput.

    Thanks.
  • JarredWalton - Thursday, August 11, 2011 - link

    All testing was done with WPA2 AES. Most modern cards do fine with that, though a few years back it was sometimes slower IIRC.
  • Musafir_86 - Thursday, August 11, 2011 - link

    -Okay, thanks for the clarification. :)
  • Yummer72 - Thursday, August 11, 2011 - link

    Thanks for the informative review.

    I wonder if Bigfoot will continue to have an advantage if the "WLAN Optimizer" program was used with the other WiFi cards?

    http://www.martin-majowski.de/wlanoptimizer/

    I have personally seen significantly improved performance and the elimination of "lag spikes" (QuakeLive) with this software tweak.

    Any comments?
  • JarredWalton - Thursday, August 11, 2011 - link

    I'll give that a try; it could very well remove the spikes, leaving the primary advantage as the lower base latency.
  • bhima - Thursday, August 11, 2011 - link

    You should review that 95% color gamut matte screen in that Mythlogic ;)
  • loopingz - Thursday, August 11, 2011 - link

    First of all thanks for highlighting that I can change my wifi adaptator on my laptop. Mine is always frozing during transfert in windows (linux is fine).

    Second thanks for helping me choosing the good one.

    I hesitate now between intel 6300 for range, correct performance and price, and the 110 2/3 for pure performance.
    May be best of two worlds intel 6300 in the eeepc that travel a lot and bigfoot in the main home laptop.

    Can I recycle a my old wifi card or a new one using an antenna and puting it in my desktop computer?

    I will give try to Wlanoptimizer too because watching movie from the raid5 nas still not perfect (router linksys e3k).

    Thanks for the good job.
  • name99 - Thursday, August 11, 2011 - link

    "Wireless networking also tends to need more overhead for error checking and interference losses, and there’s a question of whether the streams are linearly independent enough to get higher throughput, orientation, directionality of signal, etc. Even though you might connect at 450Mbps or 300Mbps, you’ll never actually reach anywhere near that level of throughput. In our testing, the highest throughput we ever saw was around 75% utilization of the available bandwidth, and that was on a 300Mbps connection."

    This is not a useful description of the situation. The nominal speed of a connection (ie the MCS index) already includes error correction overhead --- that's why you see a range of bit-rates, with the same parameters (modulation, number of streams, bandwidth) --- these different bit-rates correspond to different levels of error correction, from the strongest (1/2 coding rate) to the weakest (5/6).

    It is also unlikely that corrupt packets and the retransmission (what you are calling "interference losses", though in your environment noise is likely more relevant than interference) are substantial --- both ends aggressively modify the MCS index to get the best throughput, and try to keep the number of corrupt packets low.

    The real issue is the MAC --- the negotiations over who next gets airtime. This used to be a big deal with wired ethernet as well, of course, but it went away with switches around the time we all moved to 100TX. The basic 802.11n MAC does not rely on any real co-ordination, just on timing windows and retries, and it wastes a phenomenal amount of time. 802.11e improves the situation somewhat (I expect all the systems that get 75% efficiency are using 802.11e, otherwise they'd see around 50% efficiency), but it's still not perfect.
    What one really wants is a central arbiter (like in a cell system) that hands out time slots, with very specific rules about who can talk when. For reasons I don't understand, 802.11 has been very resistant to adding such a MAC protocol (802.11e has elements of this, but does not go full-hog), but I would not be surprised if we finally see such as part of the 802.11n successor --- it's just such an obvious place to pick up some improvement. The real problem is that to do it right you have to give up backward compatibility, and no-one wants to do that. At least if we'd had it in 802.11n, then we'd be part way to a better world (people could switch it on once all their g equipment died, eg at home).

Log in

Don't have an account? Sign up now