Like every other website on the planet, SmallNetBuilder uses cookies. Our cookies track login status, but we only allow admins to log in anyway, so those don't apply to you. Any other cookies you pick up during your visit come from advertisers, which we don't control.
If you continue to use the site, you agree to tolerate our use of cookies. Thank you!

Router Charts

Click for Router Charts

Router Ranker

Click for Router Ranker

NAS Charts

Click for NAS Charts

NAS Ranker

Click for NAS Ranker

More Tools

Click for More Tools

Wireless Reviews

Follow the Bouncing Throughput...

That being said, let's turn to the first issue that I found. While I was running some of my early tests, I kept seeing a noticeable difference in maximum throughput. At first I thought it was due to some of the interference tests that I was running, but then I decided to do a special test. I made sure that the only wireless equipment powered up was the WBR-G54 and Buffalo WLI-CB-G54 client. I then ran the NetIQ Chariot throughput.scr script for about 20 minutes, modifying only the file_size parameter to use a 200,000 Byte file size, instead of the default 100,000 Bytes for each transfer. Figure 10 shows the result.

Buffalo WBR-G54: Long throughput test

Figure 10: Long throughput test
(click on the image for a full-sized view)

This proved that I wasn't imagining the max throughput difference, and further showed a definite cyclical pattern. A similar pattern can also be seen with a cycle time of somewhere between 30 and 60 seconds. So Issue #1 is that there is work needed, probably in the transmit-rate auto ranging routine. When I presented my findings to Buffalo Tech, they confirmed the issue, and a few days later sent the plot shown in Figure 11.

Buffalo WBR-G54: Long throughput test- new firmware

Figure 11: Long throughput test - new firmware
(click on the image for a full-sized view)

The plot was generated with tweaked, unreleased firmware and although still shows a cyclical throughput variation, the variation has been reduced. So Buffalo (and presumably Broadcom) is on the problem, and says they'll be issuing a firmware update in mid-January. However, all the following results should be viewed with this issue in mind, because it can be seen in pretty much every test.

More Wireless

Wi-Fi System Tools
Check out our Wi-Fi System Charts, Ranker and Finder!

Support Us!

If you like what we do and want to thank us, just buy something on Amazon. We'll get a small commission on anything you buy. Thanks!

Over In The Forums

Hi, do you think that it would be possible to change the format of the DDNS page so that the user can input their own server details instead of having...
Hi all,My 2.4GHz wifi keeps dropping sometime in minutes of rebooting the router. The longest time it was up was 6hrs. When it goes down, there's alwa...
I just updated to firmware 384.13 and I lost all of my DHCP reservations that I had set up.I tried setting up again, but any time I reboot the router,...
If I set the setting "Wireless Mode" on the wireless adapter to "IEEE802.11ac Only", it does not see my network. It sees it if I set Wireless Mode to ...
[Release] Asuswrt-Merlin 384.13 is now available

Don't Miss These

  • 1
  • 2
  • 3