What causes the Delta % of an order to go into the red. I understand Delta is the difference in measured hashrate between the pool and nicehash, I'm just not sure what causes it? I had a fixed order that was at -100% Delta for a few mins so I was paying for hashrate that wasn't being counted by the pool, it seems strange the nicehash servers can tell the pool isn't getting the hashrate yet it continues to charge for that hashrate. I deleted the worker at the pool and created a new one with the same name which seemed to work, I just want to know what causes a negative delta % and is there anything that can be done on my end to prevent it, also why does the nicehash system allow a -100% delta rental to keep paying for hashrate they aren't showing at the pool?
Thanks
Best Regards
There are probably like 100 possible reasons why there is negative delta; I will just mention few:
- Remote pool does not respond to shares being sent (timed-out speed).
- Stale shares (remote pool rejects shares as being too late).
- Extra rewards being paid on NH for fast job switching (putting high load on miners with fast job switching causes them to not get full mining speed).
- Remote pool bans your worker thus rejecting all your shares (this one is very evil one - instead of disconnecting you, remote pool simply rejects all your valid shares - internally, it can use these shares to solve blocks, but does not reward you - we believe all MPOS pools do that and there are several large pools that are doing this nasty trick).
- Incorrect remote pool software implementation regarding diff adjustments (some pools do not honour the official stratum specifications that state =>
diff change affects all next jobs); some pools don't even send starting diff before first job (I think even ckpool does that sometimes). These shares are then rejected by the remote pool as shares above target.
- And don't forget about variance. If your pool is working with very high difficulty, miners do not. You will see more steady speed on NH, but fluctuating one on remote pool (because there are not much high shares found, but they count more). As a consequence, delta will fluctuate too. If you set extreme pool diff, you may not find a share for several minutes. In that case, remote pool speed is of course 0. But that does not mean you are not mining. All speeds are calculated out of received shares (and out of received responses from remote pool) and are therefore highly dependent on pool difficulty.
