- Articles & News
- For IT Pros
- Your Opinion
In a modern tech enthusiast’s home, it’s not unthinkable that there could be a dozen Wi-Fi devices connecting to a single access point. Just counting laptops and smartphones, how many devices there are connecting at your local coffee shop? Imagine how many there would be in a school gymnasium for a community event or a corporate board room for an all-hands executive meeting. Having 60 notebooks connect to a single AP, all of them running bi-directional traffic concurrently, isn’t far-fetched. How well a given AP performs under such conditions not only determines the quality of the end-user’s experience, but also how many APs an organization has to buy to handle an anticipated load in a given area.
Here we get our first look at how our APs stack up when getting hammered by 60 laptop clients. Trying to reflect a realistic usage scenario, we settled on the ratio of 75% downlink and 25% uplink traffic. Only four APs survived the test.
We know from our first results that optimal throughput for one client is in the 160 to 170 Mb/s range. You’ll get a sense from the iPad data coming up shortly how aggregate throughput increases for multiple, concurrent clients. But there are limits. Any given AP can only handle so much traffic before it starts to strain under the load. Even when we compared aggregate performance of one notebook against ten, Ruckus, Aruba, and HP only showed a 10% to 20% total throughput gain for the notebook group. The aggregate performance for Apple and Meraki actually dropped substantially, already forced to their knees by just ten clients.
Sixty laptops, all transferring 1 MB test files repeatedly, is a pretty heavy burden—too heavy for Apple and Meraki to sustain. Let’s take a closer look at the actual IxChariot data to see what’s really happening.
One of the qualities to look for in an access point or router is the consistency of its connections. When viewed in terms of throughput over time, you don’t want a lot of crazy peaks and troughs. You want users to have a stable connection speed, and the floor of the throughput range is at least equally important. Consider the impact on playback of a 10 Mb/s video stream when 15 Mb/s of average throughput keeps dipping down into the 3 to 5 Mb/s range.
Cisco’s flat download range here looks outstanding. The problem is that it’s so low. Incredibly, both Cisco and Apple fare far better on uplink performance than downlink, no doubt because there’s far less uplink traffic.
Ruckus offers the flattest, highest results across both data sets, with HP and Aruba both putting in impressive showings. Poor Apple’s chart is almost comical, like it managed a single downlink heartbeat before passing into the great beyond. Meraki at least flopped about in cardiac arrest for a while.