Hi,
I am testing go-ping and comparing it to a regular ping utility (Debian Linux x86_64).
I am pinging a host in LAN to have a stable testing environment. Here are the results from a ping:
285 packets transmitted, 285 received, 0% packet loss, time 286287ms
rtt min/avg/max/mdev = 0.507/0.665/0.980/0.062 ms
The problem I can see is that using a go-ping gives averages to be about 100ms higher (calling it multiple times with sending single request as in the code) and it's not uncommon to have values above 1ms which doesn't happen at all with a ping tool.
I am testing it using this code.
Here is the comparison of the resulted ping times from telegraf:
First part of the graph is a go-ping results, then I switched to a regular ping utility.
Is it a go-runtime overhead? Can we get rid of it and make the results in-pair with a regular ping tool?
Hi, I am testing go-ping and comparing it to a regular ping utility (Debian Linux x86_64). I am pinging a host in LAN to have a stable testing environment. Here are the results from a ping:
The problem I can see is that using a go-ping gives averages to be about 100ms higher (calling it multiple times with sending single request as in the code) and it's not uncommon to have values above 1ms which doesn't happen at all with a ping tool. I am testing it using this code.
Here is the comparison of the resulted ping times from telegraf: First part of the graph is a go-ping results, then I switched to a regular ping utility.
Is it a go-runtime overhead? Can we get rid of it and make the results in-pair with a regular ping tool?