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 Features

The Tests - Single STA Throughput

To shake things down and get the hang of using the EE, I started out nice and simple, using the EE to generate one virtual STA (vSTA) to check the maximum throughput of each AP with my test setup.

The results shown in Figures 9 and 10 represent the average throughput from a 5 minute IxChariot run using the throughput script with the default 1,000,000 Byte file size per timing record.

STA to AP throughput - One STA - 5min.

Figure 9: STA to AP throughput - One STA - 5min.

AP to STA throughput - One STA - 5 min.

Figure 10: AP to STA throughput - One STA - 5 min.

I started out letting the Emulation Engine use its automatic rate algorithm, but noticed lower performance than expected during my initial testing. After consulting with a CMC applications engineer, I decided to force the EE's rate to 54Mbps. This definitely improved the measured throughput for the products using the Broadcom chipset, but degraded the STA to AP speed for the 3Com and SMC Atheros-based APs.

By looking at the statistics accumulated by the Emulation Engine, I was able to see that the main contributor to the lower forced-rate speed was that vSTA transmit errors increased by about 8X when the rate was forced for the 3Com and SMC twins. I also found that the uplink speed of the Gigabyte AP was the same whether the EE rate was forced or left to autorange. I attribute this to the fact that the Gigabyte AP uses the same Atheros AR2112 radio, but the newer AR5213 MAC/baseband processor instead of the AR5212 MAC/baseband used by the 3Com / SMC AP.

So the results in Figure 9 reflect letting the EE auto-range its transmit rate for the 3Com and SMC AP runs, while being forced to 54Mbps for all the other products. All the test runs shown in Figure 10 have the EE rate forced to 54Mbps.

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

I'm using dualwan with load balancing and policy routing. Let's say I have device A, B and others. I would like to have A to use WAN1, B to use WAN1 a...
Is there a way to disable the pop-up when hovering the mouse pointer over threads?
Recently got a RT-AC86u and installed with the latest Merlin (384.18), and noticed WebUI being unresponsive after a while. Restarting the httpd servic...
I've installed last version of Asus Merlin. I have tried to install pyload but now the default version of python in entware is version 3. Pyload still...
Asuswrt-Merlin 384.19 beta is now available (except for the RT-AX56U which won't be available for this release, due to outdated GPL code).The main cha...

Don't Miss These

  • 1
  • 2
  • 3