You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I encountered a small issue while using the libp2p protocol with the Go implementation (I have not tested this with other implementations yet). I have a testbed consisting of two Linux VMs with 25 ms of artificial delay configured using tc. When using libp2p's ping, I measured around 60 ms of latency, whereas the standard ICMP ping reported about 28-30 ms. Could this additional latency be caused by libp2p using TCP, while the standard ping utility relies on ICMP?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I encountered a small issue while using the libp2p protocol with the Go implementation (I have not tested this with other implementations yet). I have a testbed consisting of two Linux VMs with 25 ms of artificial delay configured using
tc. When using libp2p's ping, I measured around 60 ms of latency, whereas the standard ICMPpingreported about 28-30 ms. Could this additional latency be caused by libp2p using TCP, while the standardpingutility relies on ICMP?Beta Was this translation helpful? Give feedback.
All reactions