For example, Windows clients have a longer inter-packet idle periods, thus resulting in lower throughput compared to Linux clients. Another finding is that device OS plays a role as well. It's been noted that CPU utilization is higher than usual and varies the most when packet sizes are small, such as for VoIP traffic. Then you can add more clients to the network or try streaming traffic to see how these affect the baseline. No other clients should be on the network. This can be done by copying a large file from a server connected via Ethernet to the wireless router, to a client device connected via Wi-Fi to that router.
One suggestion is to establish a baseline application throughput. Restart devices, stop background tasks or updates, disable antivirus, or even do a clean OS installation before starting the tests. Turn off other devices that are not part of the tests. Devices should be configured to exercise their maximum capability. Could you share some insights discovered by others during Wi-Fi performance testing?īefore starting any tests, check all cabling and configuration.Performance testing should consider these diverse real-world deployment scenarios. A stadium scenario would be heavy on video streaming or audio commentary involving thousands of clients. A dormitory scenario could include parallel video streaming, two-way video chats, online gaming, web browsing, and social media traffic. We should thus monitor buffers and CPU utilization for bursty traffic as well.Ī classroom scenario could include multicast video streaming, parallel file downloads, and background social media traffic of small packets. HTTP traffic comes in bursts as pages are loaded. Voice is periodic while video starts with a surge and then a constant rate. The idea of mixing different traffic types is that pattern of packet arrivals is different. This may include a mix of TCP and UDP data, streaming video or audio, voice calls, and a mix of mission-critical and recreational apps. To mimic real-world scenarios, a variety of traffic types coming from multiple devices must be used. Spirent TestCenter emulates multiple clients and also generates different types of traffic for testing. What traffic models should I use for Wi-Fi performance testing?.Some performance problems could be due to misconfiguration such as access point connected to the wrong switchport, poor quality cables, wrong channel assignments, or bandwidth limits unknowingly imposed. With modern Wi-Fi networks being controlled from the cloud, it's become possible to adjust a configuration, collect performance data, send it to the cloud and then evaluate if the adjustment had a positive effect. A better approach is to collect data from live networks and analyse this data. In fact, performance testing doesn't help with troubleshooting problems. Wi-Fi environment is too dynamic to reproduce performance issues. Since it's hard to use hundred of real clients, an emulation-based approach can be adopted. It's therefore important to check performance when the network is loaded with multiple busy clients. Usually a single client is used but this is far from real-world scenarios. In a typical deployment, engineers check for signal levels, coverage and throughput to ensure basic performance requirements are met. Some access points are unfair in their resource allocation.
0 kommentar(er)
