Testing pool latency on my network

[SolHarvester]

I've seen a few topics on this and want to check I'm doing it right. Since, I'm lottery mining, I don't want to worsen my chances further with high latency.

First I was using sites I've found on google to check pool latency and comes back with 180ms-190ms.

But I believe now that they are not accurate, I should instead use a tool which I installed one that is a stratum ping tool. I read it pretty much preforms the exact task a miner does to send packets to the pool and returns a ping.

I'm using ckpool, so the pool address I saved to the bat file is exactly "solo.ckpool.org:3333".
That should give me an accurate ping I should be getting for the miners on my network for that pool, right?

[BitMaxz]

What is the result after testing it with the ping tool?

have you tried the other pool from ckpool if the ping result is high you can use the other suggestion only if your ping is high.

Code:

IPV4 is solo4.ckpool.org
IPV6 is solo6.ckpool.org

Just don't forget to add the port :3333 when testing.

[DaveF]

You should also do a traceroute https://en.wikipedia.org/wiki/Traceroute
Since you are showing high latency a traceroute may help you figure out where the issue is between you and the pool.

Local network or local provider may be fixable. Something past there and there is not a lot you can do.

-Dave

[mikeywith]

But I believe now that they are not accurate, I should instead use a tool which I installed one that is a stratum ping tool. I read it pretty much preforms the exact task a miner does to send packets to the pool and returns a ping.

Correct, stratum-ping will be an exact representation of the work sent/received between you and the pool, I did mention in one of my old posts that stratum-ping could sometimes yield a very different result than using just ICMP aka ping, but I would like to state that in most cases the result will be exactly the same, so unless it's easy to perform stratum-ping (which is) it may not be worth the trouble.

Furthermore, your miner status page (assuming you do use a proper miner and software) would report what's called stale shares, that's the most accurate way to read latency between your miner and the pool, A high stale rate means there is a quiet large delay in the communication between the miner and the pool, there is no universal figure of what is accepted, but I'd say anything below 1% between stale and rejected suggest that your overall mining operation is good and you shouldn't worry, if it goes above that, there is certainly something wrong somewhere.