Wifi Latency issue

x7007 · Wed Jul 17, 2019 8:56 am

Hi,

I have PC SFP+ > CRS210-8G-2S+ > hAP Ac2 Router > Cable Modem 500/10mbps >

It's just standard connection, nothing special, just think of it as a Switch connected to Router to a modem so I have lans ports and SFP+

The weird issue is with 2.4 and 5Ghz

I have Oneplus 5T connected 2.4 or 5Ghz
I have Ambivision device that control LEDS behind the TV's both the Device and Leds are WIFI connected 2.4Ghz
I have 2 Security Wifi Cameras 2.4

If I do ping to the security cameras the ping is usually 1ms-3ms and some random jumps to 200-300 which doesn't happen ofen.
If I do ping to the OnePlus 5T I am getting jumping latency all over between 68-368 and sometimes more. But when I use the bandwidth for example going into Whatapp or speed test or youtube, the latency is reduced to 1-50ms until I finish using bandwidth
If I do ping to the Ambivision LED device when it first connected the ping is 1-10ms and then after 5-6 pings it goes up to 96-200ms and goes between high and low. Now for some reason after I changed something or did something the latency was 1-3ms ALL THE TIMES. but then after I changed settings AND REVERTED them back to the same ones it still jumps like before!

So 3 questions

What could cause the Latency to reduce to 1-2ms and then come back after the device connected again even with the reverted settings that worked just fine? and if so how can I reduce those random latency jumps, I want the minimum latency time between them.
Why when using the mobile device 2.4 or 5ghz causes high latency jumps? is it because of the power saving setting on the mobile phone?
The Security camera has low pings because they always transferring data?

Example of Ambivision LED device working fine

Reply from 192.168.1.100: bytes=32 time=3ms TTL=64
Reply from 192.168.1.100: bytes=32 time=2ms TTL=64
Reply from 192.168.1.100: bytes=32 time=2ms TTL=64
Reply from 192.168.1.100: bytes=32 time=1ms TTL=64
Reply from 192.168.1.100: bytes=32 time=1ms TTL=64
Reply from 192.168.1.100: bytes=32 time=9ms TTL=64
Reply from 192.168.1.100: bytes=32 time=4ms TTL=64
Reply from 192.168.1.100: bytes=32 time=2ms TTL=64
Reply from 192.168.1.100: bytes=32 time=2ms TTL=64
Reply from 192.168.1.100: bytes=32 time=2ms TTL=64
Reply from 192.168.1.100: bytes=32 time=79ms TTL=64
Reply from 192.168.1.100: bytes=32 time=1ms TTL=64
Reply from 192.168.1.100: bytes=32 time=2ms TTL=64
Reply from 192.168.1.100: bytes=32 time=46ms TTL=64
Reply from 192.168.1.100: bytes=32 time=2ms TTL=64
Reply from 192.168.1.100: bytes=32 time=2ms TTL=64
Reply from 192.168.1.100: bytes=32 time=2ms TTL=64
Reply from 192.168.1.100: bytes=32 time=2ms TTL=64
Reply from 192.168.1.100: bytes=32 time=8ms TTL=64
Reply from 192.168.1.100: bytes=32 time=1ms TTL=64
Reply from 192.168.1.100: bytes=32 time=1ms TTL=64
Reply from 192.168.1.100: bytes=32 time=2ms TTL=64
Reply from 192.168.1.100: bytes=32 time=2ms TTL=64
Reply from 192.168.1.100: bytes=32 time=2ms TTL=64
Reply from 192.168.1.100: bytes=32 time=4ms TTL=64
Reply from 192.168.1.100: bytes=32 time=2ms TTL=64

Example when it does the random jumps after reconnecting the Wifi AP the first seconds

Request timed out.
Reply from 192.168.1.100: bytes=32 time=8ms TTL=64
Reply from 192.168.1.100: bytes=32 time=3ms TTL=64
Reply from 192.168.1.100: bytes=32 time=3ms TTL=64
Reply from 192.168.1.100: bytes=32 time=5ms TTL=64
Reply from 192.168.1.100: bytes=32 time=7ms TTL=64
Reply from 192.168.1.100: bytes=32 time=2ms TTL=64
Reply from 192.168.1.100: bytes=32 time=1ms TTL=64
Reply from 192.168.1.100: bytes=32 time=1ms TTL=64
Reply from 192.168.1.100: bytes=32 time=63ms TTL=64
Reply from 192.168.1.100: bytes=32 time=85ms TTL=64
Reply from 192.168.1.100: bytes=32 time=107ms TTL=64
Reply from 192.168.1.100: bytes=32 time=28ms TTL=64
Reply from 192.168.1.100: bytes=32 time=49ms TTL=64
Reply from 192.168.1.100: bytes=32 time=89ms TTL=64
Reply from 192.168.1.100: bytes=32 time=91ms TTL=64
Reply from 192.168.1.100: bytes=32 time=11ms TTL=64
Reply from 192.168.1.100: bytes=32 time=33ms TTL=64
Reply from 192.168.1.100: bytes=32 time=61ms TTL=64
Reply from 192.168.1.100: bytes=32 time=97ms TTL=64
Reply from 192.168.1.100: bytes=32 time=112ms TTL=64
Reply from 192.168.1.100: bytes=32 time=73ms TTL=64
Reply from 192.168.1.100: bytes=32 time=40ms TTL=64
Reply from 192.168.1.100: bytes=32 time=72ms TTL=64
Reply from 192.168.1.100: bytes=32 time=90ms TTL=64
Reply from 192.168.1.100: bytes=32 time=108ms TTL=64
Reply from 192.168.1.100: bytes=32 time=36ms TTL=64
Reply from 192.168.1.100: bytes=32 time=45ms TTL=64
Reply from 192.168.1.100: bytes=32 time=181ms TTL=64
Reply from 192.168.1.100: bytes=32 time=100ms TTL=64
Reply from 192.168.1.100: bytes=32 time=109ms TTL=64

This is the Mobile phone without doing anything 5Ghz

Reply from 192.168.1.111: bytes=32 time=373ms TTL=64
Reply from 192.168.1.111: bytes=32 time=294ms TTL=64
Reply from 192.168.1.111: bytes=32 time=104ms TTL=64
Reply from 192.168.1.111: bytes=32 time=231ms TTL=64
Reply from 192.168.1.111: bytes=32 time=355ms TTL=64
Reply from 192.168.1.111: bytes=32 time=173ms TTL=64
Reply from 192.168.1.111: bytes=32 time=38ms TTL=64
Reply from 192.168.1.111: bytes=32 time=1ms TTL=64
Reply from 192.168.1.111: bytes=32 time=131ms TTL=64
Reply from 192.168.1.111: bytes=32 time=255ms TTL=64
Reply from 192.168.1.111: bytes=32 time=177ms TTL=64
Reply from 192.168.1.111: bytes=32 time=298ms TTL=64
Reply from 192.168.1.111: bytes=32 time=114ms TTL=64
Reply from 192.168.1.111: bytes=32 time=236ms TTL=64
Reply from 192.168.1.111: bytes=32 time=360ms TTL=64
Reply from 192.168.1.111: bytes=32 time=155ms TTL=64
Reply from 192.168.1.111: bytes=32 time=303ms TTL=64
Reply from 192.168.1.111: bytes=32 time=119ms TTL=64
Reply from 192.168.1.111: bytes=32 time=244ms TTL=64

This when doing SpeedTest 5Ghz, the 1MS at the end is the Upload test then when it's 41Ms it finished

Reply from 192.168.1.111: bytes=32 time=1ms TTL=64
Reply from 192.168.1.111: bytes=32 time=59ms TTL=64
Reply from 192.168.1.111: bytes=32 time=2ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time=108ms TTL=64
Reply from 192.168.1.111: bytes=32 time=27ms TTL=64
Reply from 192.168.1.111: bytes=32 time=49ms TTL=64
Reply from 192.168.1.111: bytes=32 time=69ms TTL=64
Reply from 192.168.1.111: bytes=32 time=90ms TTL=64
Reply from 192.168.1.111: bytes=32 time=1ms TTL=64
Reply from 192.168.1.111: bytes=32 time=32ms TTL=64
Reply from 192.168.1.111: bytes=32 time=52ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time=2ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time=20ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time=75ms TTL=64
Reply from 192.168.1.111: bytes=32 time=97ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time=4ms TTL=64
Reply from 192.168.1.111: bytes=32 time=7ms TTL=64
Reply from 192.168.1.111: bytes=32 time=14ms TTL=64
Reply from 192.168.1.111: bytes=32 time=3ms TTL=64
Reply from 192.168.1.111: bytes=32 time=7ms TTL=64
Reply from 192.168.1.111: bytes=32 time=1ms TTL=64
Reply from 192.168.1.111: bytes=32 time=3ms TTL=64
Reply from 192.168.1.111: bytes=32 time=2ms TTL=64
Reply from 192.168.1.111: bytes=32 time=9ms TTL=64
Reply from 192.168.1.111: bytes=32 time=7ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time=2ms TTL=64
Reply from 192.168.1.111: bytes=32 time=3ms TTL=64
Reply from 192.168.1.111: bytes=32 time=6ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time=1ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time=1ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time=1ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time<1ms TTL=64
Reply from 192.168.1.111: bytes=32 time=41ms TTL=64
Reply from 192.168.1.111: bytes=32 time=62ms TTL=64
Reply from 192.168.1.111: bytes=32 time=83ms TTL=64
Reply from 192.168.1.111: bytes=32 time=104ms TTL=64

mkx · Wed Jul 17, 2019 9:19 am

I guess that the weird ping pattern observed on the phone is due to power-saving kicking in when phone is idle (wireless can be power hungry and optimizing it by putting wifi chip to sleep frequently is one of first things to do). If a device is connected to AC (suppose the Ambivision gadget is) this doesn't make much sense, but it could do it anyway (if the generic wireless module does it by default and gadget devs did not think to disable that). Another possibility is that such gadget (with slow CPE) can't reply to pings quickly when it's got something else to do (like initializing who-knows-what after successful registration to wireless network).

inteq · Wed Jul 24, 2019 12:28 pm

Some sort of chipset power saving is my 1st option also for high latency on mobile phones while idle.
My Samsung Galaxy S9+ acts the same.

Wifi Latency issue

Wifi Latency issue

Re: Wifi Latency issue

Re: Wifi Latency issue

Who is online