ping times esp-idf V3.1 vs V4.1

[CharlesSeartech]

Good day,

Can somebody please inform me as to why the ping times in esp-idf V4.1 are much slower than V3.1?

V3.1 with my full application:
Pinging 192.168.3.100 with 32 bytes of data:
Reply from 192.168.3.100: bytes=32 time=2ms TTL=255
Reply from 192.168.3.100: bytes=32 time=7ms TTL=255
Reply from 192.168.3.100: bytes=32 time=2ms TTL=255
Reply from 192.168.3.100: bytes=32 time=2ms TTL=255

V4.1 esp-idf\examples\wifi\getting_started\station\main\station_example_main.c:
Pinging 192.168.3.100 with 32 bytes of data:
Reply from 192.168.3.100: bytes=32 time=89ms TTL=255
Reply from 192.168.3.100: bytes=32 time=108ms TTL=255
Reply from 192.168.3.100: bytes=32 time=107ms TTL=255
Reply from 192.168.3.100: bytes=32 time=111ms TTL=255

Pinging 192.168.3.100 with 32 bytes of data:
Reply from 192.168.3.100: bytes=32 time=67ms TTL=255
Reply from 192.168.3.100: bytes=32 time=77ms TTL=255
Reply from 192.168.3.100: bytes=32 time=73ms TTL=255
Reply from 192.168.3.100: bytes=32 time=67ms TTL=255
Second test:
Reply from 192.168.3.100: bytes=32 time=96ms TTL=255
Reply from 192.168.3.100: bytes=32 time=87ms TTL=255
Reply from 192.168.3.100: bytes=32 time=94ms TTL=255
Reply from 192.168.3.100: bytes=32 time=95ms TTL=255

V4.1 with my full application:
eply from 192.168.3.100: bytes=32 time=88ms TTL=255
Reply from 192.168.3.100: bytes=32 time=114ms TTL=255
Reply from 192.168.3.100: bytes=32 time=113ms TTL=255
Reply from 192.168.3.100: bytes=32 time=112ms TTL=255
Reply from 192.168.3.100: bytes=32 time=120ms TTL=255
Reply from 192.168.3.100: bytes=32 time=27ms TTL=255
Reply from 192.168.3.100: bytes=32 time=41ms TTL=255
Reply from 192.168.3.100: bytes=32 time=56ms TTL=255
Reply from 192.168.3.100: bytes=32 time=73ms TTL=255
Reply from 192.168.3.100: bytes=32 time=87ms TTL=255
Reply from 192.168.3.100: bytes=32 time=99ms TTL=255

My setup is a WiFi access point connected to my PC via ethernet.
Here is the scan info: ssid=TP-LINK, rssi=-42, authmode=WPA_WPA2_PSK
I am the only developer connected to the access point so there is no other traffic on the access point.

It's not just the ping that is slow to respond, all my TCP communications suffer as well.

Any help in this regard will be greatly appreciated.

Regards,
Charles

[CharlesSeartech]

Interesting phenomenon:

I did a ping while uploading a file and the ping time was much shorter:
Reply from 192.168.3.100: bytes=32 time=3ms TTL=255
Reply from 192.168.3.100: bytes=32 time=4ms TTL=255
Reply from 192.168.3.100: bytes=32 time=4ms TTL=255
Reply from 192.168.3.100: bytes=32 time=3ms TTL=255

After the upload finished the ping time was back to the past measurements:
Reply from 192.168.3.100: bytes=32 time=63ms TTL=255
Reply from 192.168.3.100: bytes=32 time=69ms TTL=255
Reply from 192.168.3.100: bytes=32 time=72ms TTL=255
Reply from 192.168.3.100: bytes=32 time=72ms TTL=255

Charles

[boarchuz]

WiFi power saving option? What happens if you esp_wifi_set_ps(WIFI_PS_NONE)?

[CharlesSeartech]

Great, thanks boarchuz, that solved the ping times.

Regards,
Charles