because you were testing against your ISPs own servers. Very often it shows inflated speeds.Myabe the 240 was a glitch (happens many times, i see 240 mbps speeds)
It is always best to test against other servers.
because you were testing against your ISPs own servers. Very often it shows inflated speeds.Myabe the 240 was a glitch (happens many times, i see 240 mbps speeds)
Even now I am.testing with airtel server from pc only its showing 118 mbps. Same server in morning showed 240.because you were testing against your ISPs own servers. Very often it shows inflated speeds.
It is always best to test against other servers.
Yes, I noticed that. To avoid these kind of erroneous speeds and confusions, it is best to test against some other server.Even now I am.testing with airtel server from pc only its showing 118 mbps. Same server in morning showed 240.
Yes and I agree but iPerf has its own purpose but is not necessary here since this is clearly not a driver/hardware issue.@enthusiast29
Call me old school, but given my hands-on experience of dealing with a myriad of WLAN modules over a decade, I would like to see a local synthetic benchmark (e.g. iPerf) rather on blindly relying on the internet-based speed test site results. That way, you can also get a rough idea regarding the actual signal-to-noise ratio on top of the RSSI data.
To check speed from ISP a simple speed test is enough over LAN.
...problem with WiFi module can be ruled out?
I understand what you're saying. I have an Intel 3160HMW chip and 5Ghz on it plagued by this behavior. Drops out to 1-2Mbps within a couple seconds of reaching full bandwidth. Sadly it's a driver issue from Intel and I can't find a single driver which doesn't have this bug and is compatible with Win10/11.Couldn't agree more, but the receptor hardware in question (MT7921) is known for its erratic behavior and sub-standard performance under load, which is why I suggested to tweak the test parameters as well.