Bitcoin Forum
April 20, 2018, 05:45:44 AM *
News: Latest stable version of Bitcoin Core: 0.16.0  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Connect to multiple pools on each GPU for redundancy  (Read 1586 times)
kcobra
Member
**
Offline Offline

Activity: 86
Merit: 10


View Profile
June 13, 2011, 03:35:49 AM
 #1

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?
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1524203144
Hero Member
*
Offline Offline

Posts: 1524203144

View Profile Personal Message (Offline)

Ignore
1524203144
Reply with quote  #2

1524203144
Report to moderator
swusc2
Sr. Member
****
Offline Offline

Activity: 305
Merit: 250


Do your part for Bitcoin!


View Profile
June 13, 2011, 03:40:27 AM
 #2

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.

Impress your friends! Buy a bitcoin keychain!
http://forum.bitcoin.org/index.php?topic=30799.0
Sukrim
Legendary
*
Offline Offline

Activity: 2324
Merit: 1002


View Profile
June 13, 2011, 12:15:25 PM
 #3

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.

https://www.coinlend.org <-- automated lending at various exchanges. No fees(!).
Mail me at Bitmessage: BM-BbiHiVv5qh858ULsyRDtpRrG9WjXN3xf
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!