How long are you waiting to see the load balance results?
It wont mine to both pools at the same time, it will switch between the two for an equal amount in a 24 hour period.
So it will give 100% hashrate to pool A for up to 12 hours, then 100% to pool B for the other 12 hours.
It works pretty much immediately for most devices.
"2D work" devices (Stratum proxy and Avalon2/3) do not support load balancing at this time.
ah okay I thought it somehow divided up the work.
Also, yes this is with stratum proxy so I guess load-balancing is completely out the window then right?
I guess in lieu of that, is there a command line I can use with cron to switch pools at certain times of the day? I assume it would be some command line rpc interface... just not familiar enough with that or where to start.
There's essentially no way to do 2D work stuff with load balancing, as the devices create their own work.
Have you tried something like --rotate? You will probably need to ensure the pools change jobs at least as often as you switch between the pools...
Yeah what I was hoping to achieve was sending something like 95% of my work to my regular pool and 5% of my work to ck's solo mining "pool"... sort of playing the lottery with 5% of my hash power. I guess I could rotate at some interval with 20 pool entries, one of which was the solo pool and the other 19 are my regular pool? Is something like that even allowed, config wise? (i.e., can I have multiple pool entries with exactly the same url, user, password?)
Other than that, I was thinking a cron job to switch pools for 5% of the day would work.
This all hinges on the idea that sending work to a solo mining effort for a short period of time even makes sense.
Everything there makes sense,
except using a centralised pool for solo mining.
I haven't thought it through yet, but maybe I could have quotas act as multipliers in rotate mode... so quota 2 with rotate of 5 minutes results in a 10 minute rotation time for that pool. Thoughts?
That'd make sense. If you commit some changes towards that sort of setup, I can pull some code from git, compile, and test.
re: using a pool for solo mining... it just saves the hassle of setting up all that is required for solo mining on my end. Also, it's probably hosted on a faster connection etc etc etc.
Also I posted this elsewhere, but I'm still trying to determine theorhetically if say 1/8 of my hash power for 24 hrs is better or worse than 8/8 of my hash power for 3 hrs, in terms of solo mining, everything else being held equal.
