Hey guys,
I just wanted to ask about cgminer mechanics for P2Pools.
Let's take e.g. doge.altpool.pw:19348. If I ping -t it in cmd, I get response around 60ms, so it's not very good, but not horrible. When I check altpool with http://doge.altpool.pw:19348/pings it shows in my browser:
{"108.48.45.12:22558": 138.49401473999023, "115.29.47.161:33570": 394.00720596313477, "37.187.90.15:8555": 23.13518524169922, "54.194.190.163:34796": 31.903982162475586, "113.240.243.138:45421": 290.53592681884766, "185.24.97.76:46659": 14.746904373168945, "186.203.198.212:8555": 239.93802070617676, "85.25.197.187:8555": 56.82015419006348, "75.158.3.37:29698": 178.71594429016113, "195.130.216.149:8555": 79.27107810974121}
When I ping every single IP from that list, some are good (like around 40-50 ms) and other are just terrible (200-300 ms). When I set my cgminer to work on doge.altpool.pw:19348 does it connect directly to altpool, that has 60 ms response, or does it connect to first avaible IP form the list above, so I could potentially end up with 200-300ms connection. I try to keep my reject rate under 10% and it happens that everything goes smooth and out of nowhere it jumps to 20 even 30% rejects.
I would be much obliged if somebody could explain how it works.
Topic: A couple of CGminer questions about P2pools (Read 388 times)
Jump to: