|
November 15, 2017, 03:00:32 PM |
|
Ok, I didn't know the latency minimum from ground to sat. New hardware can affect latency if the old systems were slow and/or overloaded compared to new equipment, but like you said, if 500ms is their (min) just for ground to sat signal travel time - reducing from 600-700ms is not likely in any significant amount.
I have read about some people getting long latency times with Hughesnet - even on Gen5 of 2000ms+ - Would that much latency be an issue for the bitcoin miners? I am network savvy, but I am not bitcoin protocol savvy yet. I would be running in a pool - probably to start with Slushpool. Any thoughts on that?
I went ahead and set up an install for next Friday of Hughesnet Gen5 - but if there are max latency or packet loss numbers I should be watching for, I'd appreciate that information. I'm thinking that latency of a second or two would not really matter - but I'm just not sure how responsive the protocol and/or the pool's hardware/software configs are to know if that's true. And about packet loss - I obviously don't want any or very very little, but is there a point where it would become a problem for mining?
Thanks!
|