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 How To

Wi-Fi System Performance

Note: "Downlink" means data flows from mesh node (AP) to client device. "Uplink" means data flows from client device to mesh node.

Multi-node Wi-Fi systems are generally designed to be in control and provide few user-settable controls. These products use a single SSID and usually don't allow channels, bandwidth or any other Wi-Fi parameters to be set, other than the network name (SSID) and encryption passphrase. So our process lets each system run as it normally would, including having a live internet connection during testing. All test traffic is run on the LAN side, however, so router throughput does not affect results.

Products are installed using their companion app or web interface. Attenuators are first set as shown in the diagram below. The root node is then installed in the Root Box-18, with the door open so that it can communicate with the smartphone running its app via Bluetooth. Once the root node is connected, the chamber door is closed. The other nodes are then added, one at a time, following the same process. If the app prompts for a firmware update, it is run until the app says all nodes are up to date. No other product settings are changed for testing.

Wi-Fi System test diagram

Wi-Fi System test diagram

After all nodes are connected and chamber doors are closed, all nodes are power cycled, with attenuators set as shown above. This lets the system come up and establish operating parameters in the exact test environment.

iperf3 is used for each throughput test with TCP/IP and default parameters, except window size is set to 2048 kb and two test streams are used. Each test is run for 90 seconds, with the first 10 seconds treated as "training" period. The "training" period data is not included in the calculated average for the rest of the test run.

The goal of the process is to measure best-case average up and downlink throughput for both bands on each node. The general test process is:

  1. Associate Pal client device to the root node 2.4 GHz radio, run down and uplink throughput tests
  2. Associate Pal client device to the root node 5 GHz radio, run down and uplink throughput tests
  3. Repeat for the one-hop and two-hop test nodes.

Attenuators 1 and 2 provide the RF paths so the Root, Hop 1 and Hop 2 nodes can form their backhaul links. The attenuation values shown are relatively low, because the path loss provided by air gap between the node and chamber antennas provides most of the loss. Path loss from the Hop 1 node to Root and Hop 2 nodes has been measured to be typically 40 dB in 2.4 GHz and 65 dB in 5 GHz using the 3 dB values shown for Attenuators 1 and 2. The goal here is to allow the branch nodes to have a signal level high enough to not cause the product to indicate that a node needs to be moved.

Testing is controlled by a script that executes the following test plan (reference above diagram):

  1. Set the attenuators as shown in diagram above
  2. Associate Pal to Root node device on 2.4 GHz. Run downlink throughput test. Run uplink throughput test
  3. Associate Pal to Root node device on 5 GHz. Run downlink throughput test. Run uplink throughput test
  4. Disassociate Pal from Root node (set Atten 5 to 63 dB). Move Pal to Hop 1 device (set Atten 4 to 0 dB).
  5. Repeat Steps 2 and 3
  6. Disassociate Pal from Hop 1 node (set Atten 4 to 63 dB). Move Pal to Hop 2 device (set Atten 3 to 0 dB).
  7. Repeat Steps 2 and 3

Results are recorded as four benchmarks. Each benchmark contains the values for Root, Hop 1 and Hop 2 nodes.

  • 2.4 GHz System Downlink throughput
  • 2.4 GHz System Uplink throughput
  • 5 GHz System Downlink throughput
  • 5 GHz System Uplink throughput.

Wi-Fi System Performance - Extender

Some Wi-Fi systems, NETGEAR's Orbi most notably, use router / extender architectures. These systems require each extender to connect only to a base router, i.e. extenders cannot be daisy-chained. These two-module systems require a slightly modified test plan.

Instead of testing a second Hop, a second set of tests is run on the Hop 1 module with the Pal-connect attenuator changed from 0 dB to 21 dB. This simulates the test client moved farther away from the extender / satellite.

The router module is installed in the Root Box-18; the Extender / Satellite is installed in the Hop 1 Box-18.

  1. Set the attenuators as shown in diagram above
  2. Associate Pal to Root node device on 2.4 GHz. Run downlink throughput test. Run uplink throughput test
  3. Associate Pal to Root node device on 5 GHz. Run downlink throughput test. Run uplink throughput test
  4. Disassociate Pal from Root node (set Atten 5 to 63 dB). Move Pal to Hop 1 device (set Atten 4 to 0 dB).
  5. Repeat Steps 2 and 3
  6. Change Hop 1 Pal-connect attenuator from 0 to 21 dB.
  7. Repeat Steps 2 and 3

Wi-Fi System Performance - Backhaul

This test measures the bandwidth from the Root node Ethernet-connected iperf3 endpoint to an Ethernet-connected iperf3 endpoint connected to Hop 1, then Hop 2. This measures the bandwidth available at each node for client and backhaul connections.

This test uses a second computer running an iperf3 server, connected via Ethernet to each node, one at a time.

  1. Confirm that all nodes are operating normally.
  2. Connect iperf3 server to Ethernet port of Hop 1 node device. Run downlink throughput test. Run uplink throughput test.
  3. Move iperf3 server from Hop 1 node device to Ethernet port of Hop 2 node device. Run downlink throughput test. Run uplink throughput test.

Results are recorded as four benchmarks:

  • Hop 1 Backhaul down
  • Hop 1 Backhaul up
  • Hop 2 Backhaul down
  • Hop 2 Backhaul up

Wi-Fi System Performance - Capacity

The test connects a single STA to each mesh node and runs simultaneous throughput tests to all three STAs. It measures how well overall system throughput is managed in a simple loading scenario. Average throughput is recorded for each STA. Only client throughput is measured, but this test also assesses how well or whether backhaul throughput is managed during the test. All test clients are 2x2.

  1. Connect Pal-24 to Root Node, set to 2.4 GHz
  2. Connect Pal-5 to Hop 1 node (5 GHz)
  3. Connect Pal-245 to Hop 2 node (5 GHz). In router / extender systems, this client will also be connected to Hop 1, i.e. the extender, but set to 2.4 GHz.
  4. Configure iperf3 for TCP/IP, two streams, 2048 kb window size,
  5. Run 30 minute test with the first 30 seconds not included in the averages reported

The test setup looks like this. Splitters have been removed for clarity. Remember, as described above, box-to-box path loss is typically 40 dB in 2.4 GHz and 65 dB in 5 GHz, which includes the 3 dB box-to-box attenuators shown.

Mesh capacity  test setup

Mesh capacity test setup

Results are recorded in two benchmarks:

  • Wi-Fi System Capacity - Downlink
  • Wi-Fi System Capacity - Uplink

Each benchmark is the total average of the throughput of the three test clients. Per-client throughput is also available by plotting the benchmarks.

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

seems there are issues with 384.7 , i have alots of wifi issues with it, never happened on the 32799 firmwarein 32799 release notes, they mention : AS...
Hello Guys,I'd like to ask your kind help because it looks like I soft-bricked my RT-N53 ASUS Router while I tried to flash the latest https://advance...
Hi,does anybody run the isc-dhcp-server on Merlin? I want to run two dhcp servers (failover) on two asus routers (one is router, one is AP). Installin...
Just got me new ac86u and trying to find out which stock or Merlin is most stable firmware. I have been reading and some people reporting issue like r...
Hey everyone, super excited to find this forum. I have some questions about setting up my home's internet network and not a lot of solid knowledge abo...

Don't Miss These

  • 1
  • 2
  • 3