(With apologies to Qualcomm)
Regular readers know I call MU-MIMO "the 3DTV of Wi-Fi" because it provides no practical benefit for most consumers. Yet manufacturers insist on churning out more products with it, including MU-MIMO even in products like 2x2 routers and extenders, where it has no chance of providing benefit. The sidebar below explains why.
The consumer Wi-Fi industry has made many missteps in rolling out MU-MIMO. First, there was the initial launch of Quantenna-based MU-MIMO "ready" AC2350/AC2400 class routers back in summer 2014. These include ASUS' first-to-market RT-AC87U and NETGEAR's R7500 Nighthawk X4. Some of these still await firmware upgrades to enable MU-MIMO.
AC2600 class routers with Qualcomm's 4x4 radio were next to market in mid-2015. Routers like Linksys' EA8500 and NETGEAR's R7800 Nighthawk X4s actually had working MU-MIMO when they shipped. But as we found in our test of six MU-MIMO enabled routers a little over a year ago, there was a big difference in total throughput gain, which is the whole point of MU-MIMO.
MU, SU Throughput difference - average
When routers using Broadcom's 4x4 radio started appearing in late 2015, MU-MIMO took another step backward. Broadcom's said its BCM4366 4x4 radio supported MU-MIMO. But it turned out the device didn't have the feature fully baked yet. So while manufacturers still slapped MU-MIMO prominently on the front of product boxes, they also buried disclaimers saying firmware upgrades were needed to turn on MU-MIMO.
To distract buyers from the absence of MU-MIMO, router makers chose to ship the new Broadcom radio in "tri-band" designs, creating gargantuan, expensive, eight-antenna AC5300/AC5400 class routers like NETGEAR's R8500 Nighthawk X8 and ASUS' RT-AC5300. The hope was that folks would get some benefit from the second 5 GHz radio and forget about the non-functional MU-MIMO.
Even when lower cost Broadcom-based dual-band AC3100/AC3150 class routers like ASUS' RT-AC88U and RT-AC3100 started shipping a few months later, working MU-MIMO firmware was still MIA. And when we finally tested a Broadcom MU-MIMO router with allegedly working MU-MIMO firmware in the form of TP-Link's Archer C3150 in August 2016, we found MU-MIMO performance so poor, that it was essentially non-functional.
It turns out that Broadcom's problems were not all in firmware, however. I learned late last year that some manufacturers have quietly been phasing a BCM4366 C0 version of Broadcom's 4x4 radio SoC into production without any visible model number or version change to products. This new version is supposedly required to produce truly functional MU-MIMO in Broadcom-based routers.
Other manufacturers like TP-Link have created a new model version like the Archer C3150 V2 and even created a new FCC ID. It's interesting that TP-Link's Class II Change letter refers to the previous BCM4366 B1 as "SU-MIMO".
MU, SU Throughput difference - average
The takeaway here is that even if you load new firmware onto your AC3100/3150/5300/5400 router, it's unlikely you'll get decent MU-MIMO performance.
The other problem working against MU-MIMO as a useful Wi-Fi technology is that devices support it have been slow to come to market, particularly in the U.S. The first mainstream U.S. phones to support MU-MIMO were Google Nexus and Samsung's Galaxy S6.
Both Google and Samsung continue to include MU-MIMO in their phones including 2x2 MU-MIMO in Google's Pixel and Samsung's Galaxy S7/S7 Edge. But if you're an iPhone fan, Apple has yet to support MU-MIMO, and perhaps never will, at least until they settle their kerfuffle with Qualcomm. Tablets supporting MU-MIMO also still aren't that common.
So the router end of MU-MIMO is a hot mess and support on the device end is nothing to write home about. But it doesn't end there. It turns out Broadcom also screwed up on the device side of MU-MIMO. Another little secret widely known by industry insiders, but by few consumers, is that Broadcom's 2x2 MU-MIMO client-side devices fall back to 1x1 mode when connected to a MU-MIMO enabled router. This happens with both Qualcomm and Broadcom-based routers; the problem is on the client side.
I was able to get my hands on a pair of Google Pixels and a pair of Samsung Galaxy S7s to test this. By the way, it's ridiculously difficult to find out the actual Wi-Fi chip used in smartphones because their Wi-Fi usually comes in a third-party module. For example iFixit's Galaxy S7 teardown calls out a Samsung 1316S7 Wi-Fi module, while Chipworks' Galaxy S7 Edge teardown identifies the Wi-Fi module as a Murata KM5D18098 that handles "5G Wi-Fi + Bluetooth". But I'm told the Pixel has Qualcomm MU-MIMO Wi-Fi buried inside and the Samsung S7 has Broadcom.
I set up a little experiment using two MU-MIMO enabled 4x4 routers, a Qualcomm based NETGEAR R7800 (V126.96.36.199 firmware) and Broadcom-based ASUS RT-AC88U (188.8.131.52_382_15850-g7402e99 firmware). The testing was done in open air with phones on shelf at opposite ends of room approximately 8' away from the router.
Because I no longer have access to ixChariot, I used octoScope's multiperf3 for testing, running four simultaneous connections with a 2048 kB TCP/IP window size. multiperf3 is a variant of iperf3 that can run simultaneous tests to multiple iperf3 servers.
The test was simple:
- Disable MU-MIMO on the router
- Associate the phones and note the device link rates
- Run multiperf3 test to measure throughput
- Enable MU-MIMO on the router
- Repeat Steps 2 and 3
The first screenshot shows the phones associated with the R7800 that had MU-MIMO disabled. Both show link rates indicating a two-stream, i.e. 2x2, connection.
Google Pixel, Samsung S7 Link Rates w/ NETGEAR R7800 - MU-MIMO off
When MU-MIMO was enabled on the router, the Pixel's link rate stayed the same, but the Samsung's dropped to the 433 Mbps indicative of a single-stream 802.11ac connection.
Google Pixel, Samsung S7 Link Rates w/ NETGEAR R7800 - MU-MIMO on
Given the 50% reduction in link rate, we'd expect the S7's throughput to be cut in half, right? Here are two S7's connected to the R7800 with MU-MIMO off...
Samsung S7 w/ NETGEAR R7800 - MU-MIMO off throughput
...and with MU-MIMO enabled. Average total throughput drops from 624 Mbps to 513 Mbps, a loss of about 18%. Not quite the 50% expected from the link rate drop.
Samsung S7 w/ NETGEAR R7800 - MU-MIMO on throughput
Now let's see how the Pixels do. MU-MIMO disabled first...
Google Pixel w/ NETGEAR R7800 - MU-MIMO off throughput
... and enabled below. With MU disabled on the R7800, total average throughput is around 616 Mbps and with it enabled, it's around 760 Mbps, a gain of about 23%. This is far from the "up to 3x faster" Qualcomm claims in its MU-MIMO promotional material, but at least still a gain.