About the failover - Is there a failover only mode (prioritized pool list) or is it only profit based mode?
I know for the failover mode workaround - using algo weights and so on, but it's very annoying if you have 10-15 pools or so.
So clean failover mode would be great - "disabling" profit switching and using pools based on a priority list.
There is a section for configuring manual pools. This works in conjunction with having the miners exit if unable to connect (which flags them as dead) to fall back to less and less profitable services. See the first post in the thread for how to configure.
So I got it up and running in "manual profit based priority" mode.
I faced couple of problems:
1. I use MRR to rent my rigs. This means pool configuration like that:
"manual": {
"account": "xxxxxx",
"sparam1": "stratum+tcp://us-central01.miningrigrentals.com:3333",
"algos": [
{ "algo": "x11 MRR", "price": 100, "fee": 0, "folder": "_APARAM1_", "command": "_APARAM2_", "arguments": "_APARAM3_ _SPARAM1_ -u _ACCOUNT_.100001 -p x", "usewindow": true },
{ "algo": "x13 MRR", "price": 100, "fee": 0, "folder": "_APARAM1_", "command": "_APARAM2_", "arguments": "_APARAM3_ _SPARAM1_ -u _ACCOUNT_.100003 -p x", "usewindow": true },
{ "algo": "x15 MRR", "price": 100, "fee": 0, "folder": "_APARAM1_", "command": "_APARAM2_", "arguments": "_APARAM3_ _SPARAM1_ -u _ACCOUNT_.100004 -p x", "usewindow": true },
{ "algo": "nist5 MRR", "price": 100, "fee": 0, "folder": "_APARAM1_", "command": "_APARAM2_", "arguments": "_APARAM3_ _SPARAM1_ -u _ACCOUNT_.100002 -p x", "usewindow": true },
{ "algo": "x11 manual", "price": 1, "fee": 0, "folder": "_APARAM1_", "command": "_APARAM2_", "arguments": "_APARAM3_ stratum+tcp://manualpool.com:3333 -u manualaccount -p x", "usewindow": true },
{ "algo": "x13 manual", "price": 1, "fee": 0, "folder": "_APARAM1_", "command": "_APARAM2_", "arguments": "_APARAM3_ stratum+tcp://manualpool.com:3333 -u manualaccount -p x", "usewindow": true },
{ "algo": "x15 manual", "price": 1, "fee": 0, "folder": "_APARAM1_", "command": "_APARAM2_", "arguments": "_APARAM3_ stratum+tcp://manualpool.com:3333 -u manualaccount -p x", "usewindow": true },
{ "algo": "nist5 manual", "price": 1, "fee": 0, "folder": "_APARAM1_", "command": "_APARAM2_", "arguments": "_APARAM3_ stratum+tcp://manualpool.com:3333 -u manualaccount -p x", "usewindow": true },
]
}
So my miner will automatically start mining to one of the MRR pools (high "profitability" with price:100) if anybody rents some of them. So far so good, but let's say X15 MRR is rented.
Miner Control (MC) starts in auto mode:
- Mining at X11 MRR - MC tries 3 times with 10s pause (-r 3 -R10) total of 30s before it declares pool as dead
- Mining at X13 MRR - there it goes another 30s
- Starts mining at X15 MRR which will be alive.
- switchtime is 2min - even better to be 1min, because I'd want my renter to get his hashrate sooner. That means every 2min of mining will be followed by 1min of waiting when declaring dead pools.
It will be even worse if there is no rented rig (all MRR are dead) - there will be at least 2min pause every switchtime...
Am I missing something? Maybe there is another way to do it?
I think it would be the ideal way if MC could check for pools viability before switching to them?
And then switches to the first alive pool going from the most profitable down...
2. Had to define more "algos" so I can tell different pools in "manual" service even though both pools use same algorithm. (cosmetic issue, more of annoyance but not functionality)
Example:
{ "name": "x11 NiceHash", "hashrate": 5435, "power": 49, "aparam1": "C:\\CryptoMining\\ccminer-maxwell-optimized-1.47.sp", "aparam2": "ccminer.exe", "aparam3": "-q -r 3 -R 10 -a x11 --no-color -o" },
{ "name": "x11 Blackcoinpool", "hashrate": 5435, "power": 49, "aparam1": "C:\\CryptoMining\\ccminer-maxwell-optimized-1.47.sp", "aparam2": "ccminer.exe", "aparam3": "-q -r 3 -R 10 -a x11 --no-color -o" },