Introducing CherryPicking - new Windows & Linux Pool Hopper

[amazingrando]

I'm trying to keep up with each of the pools and their status.  This is what I have right now.  Is this how others have their pools configured?  Are there others I could/should add or disable?

0arsbitcoin          Backup
1bitclockers        Disabled - may work with 0.6.5
2bitcoinlc           Disabled - may work with 0.6.5
3bithasher           Ok
4eclipsemc           Ok
5eligius           Backup
6mainframe           Ok
7mineco           Ok
8mtred           Ok
9nofee           502 error (temporarily down?)
10ozco           Ok
11polmine           Disabled - may work with 0.6.5
12rfcpool           Disabled - pool shutdown
13slush           Ok
14triple           Ok
15unitedminers   Ok, but recent site/connection problems
16BitcoinPool   Disabled - may work with 0.6.5
17btcserv           Ok - required new cfg (8/15)
18poolmunity   Disabled
19bitp           Disabled
20Bloodys           Ok
21BtcMonkey   Ok
22BTCPool24   Ok
23BTCWorld           Ok
24DigBtc           Ok
25NinjaCoin           Ok
26ABCPool           Backup

[1713921087]

1713921087

[ampirebus]

Anyway, I've got something to show, from a testing version of v0.6.5:

Code:

* Updating pools
* polmine
* Pool update done
	Type: PROP
	Hash rate: 153.76 GH/s
	Monitoring mode: TIME
	Round time: 41254
[/quote]

 

[amazingrando]

Question about the picking algorithm.  In the case below, it would seem that unitedminers would be the most efficient, but instead it chooses btcserv.  Curious as to why:

Code:

* 15unitedminers
* Pool update done
        Type: PROP
        Hash rate: 1.722 GH/s
        Round shares: 305245
        0.37583496908961384
* 17btcserv
* Pool update done
        Type: PROP
        Hash rate: 21.231 GH/s
        Round shares: 748654
        0.9217852968887803
* 20Bloodys
* Pool update done
        Type: PROP
        Hash rate: 2.84 GH/s
        Round shares: 1853551
        2.2821971950106397
* 21BtcMonkey
* Pool update done
        Type: PROP
        Hash rate: 2.066 GH/s
        Round shares: 3908522
        4.812394126213617
* 22BTCPool24
* Pool update done
        Type: PROP
        Hash rate: 27.789 GH/s
        Round shares: 3678697
        4.529420541810857
* 23BTCWorld
* Pool update done
        Type: PROP
        Hash rate: 4.35 GH/s
        Round shares: 2296943
        2.8281265914449207
* 24DigBtc
* Socket timeout
* Read timed out
* Update error or pool considered invalid (lagging or down)
* 25NinjaCoin
* Socket timeout
* Read timed out
* Update error or pool considered invalid (lagging or down)
* 26ABCPool
* Pool update done
        Type: PPS
        Hash rate: 80.3 GH/s
        1.012453300124533
* Most efficient pool is: 17btcserv
0.9217852968887803
* Cherry Picking!

[Bloodred]

I'm guessing you're using STATIC_FAST, which chooses the fastest pool under 1.0, if you switch to NORMAL it'll always go to the lowest pool.

[scatterbrain]

Any eta on v0.6.5? Those tests of the new time method look promising. I see a btc donation in your future bloodred

[amazingrando]

I'm guessing you're using STATIC_FAST, which chooses the fastest pool under 1.0, if you switch to NORMAL it'll always go to the lowest pool.

Yes, I'm using STATIC_FAST.  Should I switch to NORMAL until the new algorithm in 0.6.5?

[Bloodred]

Any eta on v0.6.5? Those tests of the new time method look promising. I see a btc donation in your future bloodred

Should be coming later today or tomorrow.

I'm guessing you're using STATIC_FAST, which chooses the fastest pool under 1.0, if you switch to NORMAL it'll always go to the lowest pool.

Yes, I'm using STATIC_FAST.  Should I switch to NORMAL until the new algorithm in 0.6.5?

NORMAL should, in theory, have the best efficiency but also higher variance.

[Bloody Angel]

Is there any compiled poclbm Miner where the improved phatk OpenCL Kernel from this thread: https://bitcointalk.org/index.php?topic=25860.0 is running with CherryPicking?

I hope you can give a Link to one, because all I tested didn't work :-(


Thank you.


Bye Bloody



PS: Nice work!

[Bloodred]

Phoenix currently isn't supported, as for poclbm you can use any version as long as it accepts the same command line arguments (and ideally has the same console output).

[tal0n4]

I'm trying to keep up with each of the pools and their status.  This is what I have right now.  Is this how others have their pools configured?  Are there others I could/should add or disable?

0arsbitcoin          Backup
1bitclockers        Disabled - may work with 0.6.5
2bitcoinlc           Disabled - may work with 0.6.5
3bithasher           Ok
4eclipsemc           Ok
5eligius           Backup
6mainframe           Ok
7mineco           Ok
8mtred           Ok
9nofee           502 error (temporarily down?)
10ozco           Ok
11polmine           Disabled - may work with 0.6.5
12rfcpool           Disabled - pool shutdown
13slush           Ok
14triple           Ok
15unitedminers   Ok, but recent site/connection problems
16BitcoinPool   Disabled - may work with 0.6.5
17btcserv           Ok - required new cfg (8/15)
18poolmunity   Disabled
19bitp           Disabled
20Bloodys           Ok
21BtcMonkey   Ok
22BTCPool24   Ok
23BTCWorld           Ok
24DigBtc           Ok
25NinjaCoin           Ok
26ABCPool           Backup

I am using the exact same configuration right now. Is mainframe actually working for you? I've been running CP since 8/8 and mainframe has never connected for me. I always get this error:

15-08-11 03:24:48 * 6mainframe
15-08-11 03:24:48 * Update error or pool considered invalid (lagging or down)

[amazingrando]

Thanks for the feedback!

Mainframe has never worked for me.  Not sure why that is.  But I only added it into my pools list yesterday, so I wasn't sure if it was temporary or not. 

[tal0n4]

OK, good to know its not just me... 

[Bloody Angel]

Is there any disadvantage if I set the UpdateTime to 60 Seconds?

The Miners are not disconnecting when a update is running right?

Bye Bloody

[Bloodred]

There's no disadvantage and the miners don't stop for updates. The only possible problem is that it may or may not be more obvious to pool operators that are against hopping if they have some system that checks how often you request their stats pages. Note that the minimum value is 30s, if you set something less than that it will be switched internally to 30s without any explicit messages.

[ditchmagnet]

I am having trouble getting setup.

I am just testing with bitcoins.lc for now since I already had miners setup.

I am just trying to get one miner going but it keeps saying:

[Miner0] 127.0.0.1:8332 Problems communicating with bitcoin RPC

I thought I had the cfg file for pools and for the bitcoinlc cfg set right.

I also copied the cert file for java.

[amazingrando]

OK, good to know its not just me... 

It seems like their API is working http://mining.mainframe.nl/api

I wonder if they've blacklisted the CP client somehow?

[hawks5999]

take my word for it: don't spend any time trying to get mainframe working...
my payout from mainframe has been awful:

avg pps, poolname, eff
0.0000202594021739130   Mainframe      77%


all it has done is lower my overall efficiency: disabled.

[amazingrando]

take my word for it: don't spend any time trying to get mainframe working...
my payout from mainframe has been awful:

avg pps, poolname, eff
0.0000202594021739130   Mainframe      77%


all it has done is lower my overall efficiency: disabled.

Yikes, that is bad.  Disabled it is!

Thanks

[Bloodred]

I am having trouble getting setup.

I am just testing with bitcoins.lc for now since I already had miners setup.

I am just trying to get one miner going but it keeps saying:

[Miner0] 127.0.0.1:8332 Problems communicating with bitcoin RPC

I thought I had the cfg file for pools and for the bitcoinlc cfg set right.

I also copied the cert file for java.

Delete poclbm and download it again, that's a poclbm problem and this seems to be the quickest solution.

[ditchmagnet]

yep, was just about to post that.

I was trying to use the path to guiminer, but I re-downloaded just poclbm and it is working now.

Thanks.