I’m running a Wi-Fi survey using NetSpot and noticed that it’s taking about 10 minutes to scan one of the measurement points. This is unreasonably long.
The only odd thing is that this network (SSID) has a speed limit of 10 Mbps. I suspect this limitation is slowing down the process.
Has anyone encountered this?
Can a bandwidth limit affect the measurement time so significantly?
Is there anything I can tweak in NetSpot’s settings to speed up the scanning of such a slow network?
Yeah, that would make sense. If the SSID is capped at 10 Mbps, then anything that depends on pushing a certain amount of test data is going to take longer. So if one SSID is much slower than the others and also happens to have a bandwidth limit, that’s the first thing I’d suspect.
Exactly. If you’re doing active measurements, the throughput limit can absolutely stretch out the time per point. You’re basically trying to measure performance through a pipe that’s intentionally narrow, so the test itself has less room to finish quickly.
@ShadowBoxer_88 Is there a way to speed things up through the settings, or is this beyond repair with such a speed limit on the SSID?
In NetSpot, one of the first things I’d look at is the packet size / amount of data being transferred during the test. If that’s set higher, a capped SSID is naturally going to take longer to finish each point. Reducing that can help speed things up. So yeah, if the network is limited to 10 Mbps, I’d try making the test lighter first instead of assuming every point just has to take 10 minutes.
If the SSID is bandwidth-limited, long measurements are not that surprising. If you want to reduce the time, lower the amount of data the test is trying to push per point. And if that network is only there for a specific low-bandwidth use case, you may also want to ask whether you really need the same measurement method on it as on a normal SSID.