WiFi request far slower than Ethernet

Official Hardware Portenta Family Portenta H7
1

I know WiFi has more latency than ethernet, but the difference in the requests is 22ms for Ethernet to 2-9 whole seconds for 14 bytes of data saying "Hello World". WiFi signal is consistently around -57 dB which is really good. Timing my code using micros, my request only takes 1-3 ms to process. There just is a huge delay afterwards.

Do other people see the same type of delays doing a basic GET request to their portenta? My assumption is the WiFi module is going to sleep between requests. If I spam requests ASAP the times eventually drop down to 100-300ms which is more reasonable, but less than a second of idle time and the next request will take seconds.

2

Yes, I recognize the much larger WiFi latency than Ethernet, even in local network.

Hereafter is the ping results to compare

  1. WiFi
kh@kh-Inspiron-3593:~$ ping portenta-h7-m7.local
PING portenta-h7-m7.local (192.168.2.94) 56(84) bytes of data.
64 bytes from 192.168.2.94 (192.168.2.94): icmp_seq=1 ttl=255 time=49.4 ms
64 bytes from 192.168.2.94 (192.168.2.94): icmp_seq=2 ttl=255 time=153 ms
64 bytes from 192.168.2.94 (192.168.2.94): icmp_seq=3 ttl=255 time=73.4 ms
64 bytes from 192.168.2.94 (192.168.2.94): icmp_seq=4 ttl=255 time=95.7 ms
64 bytes from 192.168.2.94 (192.168.2.94): icmp_seq=5 ttl=255 time=119 ms
64 bytes from 192.168.2.94 (192.168.2.94): icmp_seq=6 ttl=255 time=22.0 ms
64 bytes from 192.168.2.94 (192.168.2.94): icmp_seq=7 ttl=255 time=30.4 ms
64 bytes from 192.168.2.94 (192.168.2.94): icmp_seq=8 ttl=255 time=47.7 m
  1. Ethernet
kh@kh-Inspiron-3593:~$ ping portenta-h7-m7-15.local
PING portenta-h7-m7-15.local (192.168.2.87) 56(84) bytes of data.
64 bytes from 192.168.2.87 (192.168.2.87): icmp_seq=1 ttl=255 time=0.964 ms
64 bytes from 192.168.2.87 (192.168.2.87): icmp_seq=2 ttl=255 time=0.216 ms
64 bytes from 192.168.2.87 (192.168.2.87): icmp_seq=3 ttl=255 time=1.07 ms
64 bytes from 192.168.2.87 (192.168.2.87): icmp_seq=4 ttl=255 time=4.40 ms
64 bytes from 192.168.2.87 (192.168.2.87): icmp_seq=5 ttl=255 time=0.314 ms
64 bytes from 192.168.2.87 (192.168.2.87): icmp_seq=6 ttl=255 time=0.635 ms
64 bytes from 192.168.2.87 (192.168.2.87): icmp_seq=7 ttl=255 time=0.996 ms
64 bytes from 192.168.2.87 (192.168.2.87): icmp_seq=8 ttl=255 time=4.47 ms

I suggest you post an issue on ArduinoCore-mbed mbed_portenta core to address the problem.

3

Hm, ours seems reasonably normal 30ms isn't too bad. When mine is 3 entire seconds. I'll ask there.

4

There is probably a few more jumps with the WiFi and Ethernet is probably several orders of magnitude faster. It appears you are not comparing as they say apples to apples.

5

3 seconds isn't expected. I'm not complaining about 30 ms. I'm complaining about 3+ second request time when less than 3 ms is my code.

6

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.