Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reset Diff at Algo Change #77

Open
pr0vieh opened this issue Nov 7, 2018 · 4 comments · May be fixed by inteI-cloud/nodejs-pool#4
Open

reset Diff at Algo Change #77

pr0vieh opened this issue Nov 7, 2018 · 4 comments · May be fixed by inteI-cloud/nodejs-pool#4

Comments

@pr0vieh
Copy link

pr0vieh commented Nov 7, 2018

hi,

i have tested your miner a while and i see a big problem...

if the algo changed from e.g. cn1/lite the diff is very high because high hash rates!
but it drop from ~900h/s to ~250h/s at cn2 with a diff @900h/s it takes too long to adjust the diff!!
algochange2

this Algo Change wars nearly useless is think...

@MoneroOcean
Copy link
Owner

It is not such a big issue IMHO. Diff is not so important unless pool is overload with low diff shares and it is not.

@pr0vieh
Copy link
Author

pr0vieh commented Nov 7, 2018

that's not what I mean...

take a look at the time...
my miner has no gain for about 8 min then Algo Change!
because the diff is too high for CN2 or xtl !!
but ok for cn-lite/1 !!!
force lowering Diff faster for Algo Change from cn-lite to cn/2 or something else!
the H/s drop from ~ 700H/s to 150H/s with a Diff of 18709 that's too much

@MoneroOcean
Copy link
Owner

This is exactly what I mean. It is not a big issue that your miner do not submit result for 8 minutes. It is normal situation even if you setup diff for 30 seconds. It just mean low luck period that it normal stuff from time to time and on average it will not affect your earnings.

@pr0vieh
Copy link
Author

pr0vieh commented Nov 7, 2018

but this mass of Hash's lost for me at moment... and these two founds @example are really lucky i see AlgoChanges without any found @cn/2 after cn-lite and 10 min later switch back to cn-lite (means the algo change was completely useless!)
and the target diff @cn/2 at your pool with this miner is normally at half of this but its only to high after mining cn-lite... normal cn/s target diff toggles between ~5000 and ~8000 @180H/s this is ok for sure! fact is after cn-lite the diff is too high and falls too slowly that would have a lot of optimization potential...
this is only an hint to you to make things more optimal...
i think i turn off cn-lite for my miners at moment...

i really like your whole idea ❤️ 👍 👍 let fill up the 🌊 😎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants