|
Title: Connect to multiple pools on each GPU for redundancy Post by: kcobra on June 13, 2011, 03:35:49 AM It has been suggested in the forums that one should run two or more miners against each GPU, with each minor hitting a different pool. That away if one pool goes down because of a ddos attack or similar the other minor will take up the slack.
People say to set the aggression level low on the second minor so it will only take up 1-2 mh/s while the main miner is running. Then in theory when the main minor goes down the second minor should ramp up to normal speeds. In order to accomplish a 1-2 mh/s on the second minor I have to set the aggression all the way down to 1. The problem I have is when the main minor goes down the second one only kicks up to around 13 mh/s, because of the low aggression. Anyone got ideas on what I am doing wrong? Title: Re: Connect to multiple pools on each GPU for redundancy Post by: swusc2 on June 13, 2011, 03:40:27 AM I have a similar issue. But I just run two pools at the same time at the same aggression. It seems to work out fine for me you just don't have Primary or Secondary. It just distributes it when both are up and when one goes down it just distributes all work to that one.
Title: Re: Connect to multiple pools on each GPU for redundancy Post by: Sukrim on June 13, 2011, 12:15:25 PM I have a similar issue. But I just run two pools at the same time at the same aggression. It seems to work out fine for me you just don't have Primary or Secondary. It just distributes it when both are up and when one goes down it just distributes all work to that one. Me too - in theory I could run a miner for each of the bigger pools out there and reduce variance with this significantly as I would earn a little bit on every block these pools find. |