Large increase in job switching after new release

Maznoz
Archived posts: 27
Joined: Sep 03, 2015

Large increase in job switching after new release

by Maznoz · · Post #2065

Hi,

first I like to say I like the new features and graphs!

However I've noticed a huge increase in the job switching resulting in suboptimal mining for me, possible after the new release. I've first noticed this behaviour around 10:30 Amsterdam time (8:30 UTC).

I have just started mining here a couple of weeks ago and used the "r=..." parameter to tweak my work restart delay. Currently I don't notice much difference between no "r" parameter at all, "r=5" or "r=10".

Any idea what is going on? I really liked this pool the last couple of weeks and I hope I can keep mining here.

Best,
Maznoz
Steve Sokolowski avatar
Steve Sokolowski
Archived posts: 4559
Joined: Aug 27, 2014

Re: Large increase in job switching after new release

by Steve Sokolowski · · Post #2066

There might be some emergent behavior from the change we made last night to make block times more accurate on networks that switch frequently.

For now, I temporarily disabled that feature, so the behavior of the mining server will be identical to what it was before the release. All other features are unaffected. If the switches continue, it may be that switching so often is actually the correct choice because the time lost in switching is still better than mining litecoins.

Let me know what happens now.
Steve Sokolowski avatar
Steve Sokolowski
Archived posts: 4559
Joined: Aug 27, 2014

Re: Large increase in job switching after new release

by Steve Sokolowski · · Post #2075

No, there's only a way to include coins. Excluding coins is tricky, because that means that we need to come up with a formula to determine how much such exclusions should be penalized for bringing down the pool's profitability.

I think we can do more work on this issue during the evening or this weekend to optimize it, now that we have the code deployed. Changes to a few configuration values may be all that is necessary.