Our own Sebastian Peak has delved into the nightmare world of testing WiFi, specifically MU-MIMO and explained some of the difficulties you encounter when testing wireless networks. It is now Ars Technica's turn to try to explain why your 2.4GHz router never delivers the advertised 1,000 Mbps as well as how to test your actual performance. As with many products, the marketing team has little interest in what the engineers are saying, they simply want phrases they can stick on their packaging and PR materials. While the engineers are still pointing out that even the best case scenarios involving a single user less than 10 feet away, with clear line of sight will not reach the theoretical performance peak, the PR with that high number has already been emailed and packages are printing.
Drop by Ars Technica for a look at how the current state of WiFi has evolved into this mess, as well as a dive into how the new technologies work and what performance you can actually expect from them.
"802.11n was introduced to the consumer public around 2010, promising six hundred Mbps. Wow! Okay, so it's not as fast as the gigabit wired Ethernet that just started getting affordable around the same time, but six times faster than wired Fast Ethernet, right? Once again, a reasonable real-life expectation was around a tenth of that. Maybe. On a good day. To a single device."
Here is some more Tech News from around the web:
- AMD Ryzen with VMWare ESXi: A Pink Screen of Death @ [H]ard|OCP
- Windows 10 Build 15048 Has a Windows Mixed Reality Demo You Can Try @ Slashdot
- User rats out IT team for playing games at work, gets them all fired @ The Register
- If we must have an IoT bog roll holder, can we at least make it secure? @ The Register
- Microsoft wants you to plan a new generation of legacy systems @ The Register
- Nintendo tells Switch users that dead pixels are not its problem @ The Inquirer
- One million decrypted Gmail and Yahoo accounts for sale on the bloody dark web @ The Inquirer
- The iflix HD Streaming Q&A With Ash Crick @ TechARP