search

jankejc / private-5g-ul-thrpt-dl-lat

Repo that has evolved from research project to master thesis.
0 stars 0 forks source link

2s ping is not 2s ping 🤔 #25

Closed jankejc closed 1 week ago

jankejc commented 1 week ago

PING 10.15.20.184 (10.15.20.184) 64(92) bytes of data. 72 bytes from 10.15.20.184: icmp_seq=1 ttl=64 time=22.5 ms 72 bytes from 10.15.20.184: icmp_seq=2 ttl=64 time=29.5 ms 72 bytes from 10.15.20.184: icmp_seq=3 ttl=64 time=19.6 ms 72 bytes from 10.15.20.184: icmp_seq=4 ttl=64 time=17.6 ms 72 bytes from 10.15.20.184: icmp_seq=5 ttl=64 time=22.7 ms 72 bytes from 10.15.20.184: icmp_seq=6 ttl=64 time=23.7 ms 72 bytes from 10.15.20.184: icmp_seq=7 ttl=64 time=24.7 ms 72 bytes from 10.15.20.184: icmp_seq=8 ttl=64 time=25.5 ms 72 bytes from 10.15.20.184: icmp_seq=9 ttl=64 time=29.5 ms 72 bytes from 10.15.20.184: icmp_seq=10 ttl=64 time=20.7 ms

--- 10.15.20.184 ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 1809ms rtt min/avg/max/mdev = 17.635/23.620/29.542/3.694 ms

What should we do? There are 10 packets with intercal 0.2s... should be okay.

jankejc commented 1 week ago

It's 1809 ms, not much off from 2000 ms. Do we really need exactly 2000 ms?

jankejc commented 1 week ago

The first packet is sent immediately without waiting. Therefore, with a count of 10, the total time will be around 1800 ms instead of 2000 ms. This can be fixed. Running 11 pings instead of 10 is one way.

jankejc commented 1 week ago

So the question is, do we want the time to always be a few milliseconds higher than expected or a bit lower than expected time (lower by less than 1 interval)?

jankejc commented 1 week ago

after meeting with supervisor We don't need to look at this.