Open Jieiku opened 1 year ago
It depends on what the timing source is.
The ICMPPingEngine uses QElapsedTimer to measure the duration and the source for that is determined by Qt/the OS, my use case was never for seeing pings that low since I was interested in the ping times to an external host.
You'd need to look at QElapsedTImer and determine what timer it is actually using, assuming that it's purely the timer and not some other processing, Pingnoo is multithreaded because has to have pings running with different TTL concurrently and therefore each reply requires a map lookup to find the ping request that matches the response we just got.
If it's purely a timer issue then it would require per-os specific code to make use of whatever high performance counter the OS supplies, I use QElapsedTimer because it works everywhere, but it will give different results on different platforms because it's at the mercy of whatever timer Qt decided to bind it to.
When I use regular ping or gping to ping my gateway I see ping times that are a fraction of a millisecond. ( 0.12 ms )
When I use pingnoo to do the same thing I see ping time of around 4ms (30+ times larger than what ping or gping report).
My OS is Arch, The title bar of pingnoo shows this:
I installed using the AUR, this does appear to be the latest release: https://github.com/nedrysoft/pingnoo/releases
Does anyone have any Idea why I would see such a discrepancy?
gping:
pingnoo: