Re: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 10000 miners
Thanks - that's sort of what I'm talking about. I actually don't mind using auto-exchange to BTC, but it's really not even perfect for that because there's still down time and ramp-up time with the miner. For example, I watched earlier today where I was mining X17 on ahash, then it switched to X17 Zerg, then back to X17 on ahash all within 5 min.
It would be really nice if there was a checkbox in the Profit Switching tab that said something like "Don't switch pools on same algorithm". Doesn't seem to me like it would be that difficult to implement.
Ahh, so you're meaning same algo but between different multipools. This is harder, but to mitigate the issue, make sure you use 24h actual for statistics. I personally found that both 24h Estimate and of course, Current, skews the profit/MH figure, and ended up with unnecessary switching.
Most Yiimp pools, depend on if they can normalize and if the normalization is applied optimally. they base the 24 Estimate on the recently found blocks, so if they got lucky and hit 2 blocks in a row in a relatively short time, that is usually enough to skew the reported profit to AM and cause you to switch. By the time you switched to them, you usually ended up on the unlucky round(s) as per Murphy's Law...and as a result, not earning as much as you would've expected according to what is being reported.
at least the 24h actual uses much longer period for averaging the reported profit and hence, less swing on the profit rate and less unnecessary switching.
Yeah the 24 hr actual will switch less, but I want to ride the difficulty dips. Sometimes it works great if the pool finds a few blocks during those dips, and sometimes it doesn't if the dip is short-lived, but I've generally had good results if I keep my switching % threshold high enough. Some other tools have interesting compromises:
- NemosMiner Plus uses a trust mechanism that combines the 24 hr actual with current estimates
- Crypto GUI Miner seems to store avg difficulties over different time thresholds (i.e. 1 hr, 3 hr, 6 hr, etc.), although their calculator has other problems
I would love it if AM could incorporate one of these ideas, or even just add that "Don't switch pools on same algorithm" checkbox
