Quote from: ericisback on March 17, 2014, 01:52:02 PM

Quote from: mdude77 on March 17, 2014, 01:33:21 AM

I have my rigs split across pools to minimize variance.

M

I'm fairly new to mining; however, I have read that balancing your hash rate between pools is a best practice, to minimize variance. I'm assuming that just choosing "(b)alanced" from the "[C]hange Management Strategy" option in BFGMiner, is all I have to do (if I already have multiple pools listed in the command line), correct? BFGMiner is telling me it is "Connected to multiple pools without LP".

What is "LP"?

When using BTC Guild as one of multiple pools, is there any disadvantage to using this strategy (slower share acceptance, etc.)?

Finally, when I am connected to multiple pools, only BTC Guild (pool 0 in my example) seems to be requesting regular work updates. Is this normal? FWIW, all pools are accepting shares normally (best I can tell)

Wow, I asked four questions... I feel like a hog sometimes...

LP is longpoll. That was the protocol used before the creation of ASICs. Now mostly everyone is using stratum.

I've never used the load balancing in cgminer (bfgminer is a clone of cgminer, so I assume same functionality). When I say I balance between pools, I mean I have one miner pointed to one pool, and another miner pointed to another pool, with each using each other's pool as a backup.

M