Introducing CherryPicking - new Windows & Linux Pool Hopper

[scatterbrain]

been running fast additive_1 for about 2 days now and i noticed that it's picking eligius, a PPS pool, over mtred, a PROP pool which is currently at .094163...this shouldn't be happening should it? i saw this earlier in another situation with bitclockers as well. i'm not getting any errors or anything, it just seems to be prioritizing the PPS pool over the a PROP pool with efficiency way under 1. i changed it to fast additive_2 and it did the same thing. i'll upload the full log for you when i get home bloodred but thought you should know in the meantime. also, no connection issues at all with either pool

18-08-11 08:18:35 * Updating difficulty
18-08-11 08:18:35 Difficulty is: 1805700.8361937
18-08-11 08:18:35 * Updating pools
18-08-11 08:18:35 * 0arsbitcoin
18-08-11 08:18:36 * Pool update done
18-08-11 08:18:36    Type: PPS
18-08-11 08:18:36    Hash rate: 426.032 GH/s
18-08-11 08:18:36    1.0023472415217636
18-08-11 08:18:36 * 1bitclockers
18-08-11 08:18:38 * Pool update done
18-08-11 08:18:38    Type: PROP
18-08-11 08:18:38    Hash rate: 245.29 GH/s
18-08-11 08:18:38    Monitoring mode: SHARES
18-08-11 08:18:38    Round shares: 1117624
18-08-11 08:18:38    1.43939988800921
18-08-11 08:18:38 * 2bitcoinlc
18-08-11 08:18:39 * Pool update done
18-08-11 08:18:39    Type: PROP
18-08-11 08:18:39    Hash rate: 508.831 GH/s
18-08-11 08:18:39    Monitoring mode: SHARES
18-08-11 08:18:39    Round shares: 1194961
18-08-11 08:18:39    1.5390030364195595
18-08-11 08:18:39 * 3bithasher
18-08-11 08:18:40 * Pool update done
18-08-11 08:18:40    Type: PROP
18-08-11 08:18:40    Hash rate: 3.76 GH/s
18-08-11 08:18:40    Monitoring mode: SHARES
18-08-11 08:18:40    Round shares: 1706755
18-08-11 08:18:40    2.198147995980007
18-08-11 08:18:40 * 4eclipsemc
18-08-11 08:18:40 * Pool update done
18-08-11 08:18:40    Type: SCORE
18-08-11 08:18:40    Hash rate: 75.14 GH/s
18-08-11 08:18:40    Monitoring mode: SHARES
18-08-11 08:18:40    Round shares: 2481512
18-08-11 08:18:40    13.742652992457298
18-08-11 08:18:40 * 5eligius
18-08-11 08:18:41 * Pool update done
18-08-11 08:18:41    Type: PPS
18-08-11 08:18:41    Hash rate: 500.363 GH/s
18-08-11 08:18:41    1.0019985490533871
18-08-11 08:18:41 * 6mainframe
18-08-11 08:18:41 * Update error or pool considered invalid (lagging or down)
18-08-11 08:18:41 * 7mineco
18-08-11 08:18:42 * Pool update done
18-08-11 08:18:42    Type: PPLNS
18-08-11 08:18:42    Hash rate: 99.385 GH/s
18-08-11 08:18:42    Monitoring mode: SHARES
18-08-11 08:18:42    Round shares: 2564738
18-08-11 08:18:42    1.8730312242688978
18-08-11 08:18:42 * 8mtred
18-08-11 08:18:42 * Pool update done
18-08-11 08:18:42    Type: PROP
18-08-11 08:18:42    Hash rate: 291.585 GH/s
18-08-11 08:18:42    Monitoring mode: SHARES
18-08-11 08:18:42    Round shares: 73113
18-08-11 08:18:42    0.09416301368977167
18-08-11 08:18:42 * 9nofee
18-08-11 08:18:42 * Update error or pool considered invalid (lagging or down)
18-08-11 08:18:42 * 10ozco
18-08-11 08:18:44 * Pool update done
18-08-11 08:18:44    Type: PROP
18-08-11 08:18:44    Hash rate: 54.525 GH/s
18-08-11 08:18:44    Monitoring mode: SHARES
18-08-11 08:18:44    Round shares: 1265174
18-08-11 08:18:44    1.6294311091316616
18-08-11 08:18:44 * 11polmine
18-08-11 08:18:45 * Pool update done
18-08-11 08:18:45    Type: PROP
18-08-11 08:18:45    Hash rate: 138.82 GH/s
18-08-11 08:18:45    Monitoring mode: TIME
18-08-11 08:18:45    Round time: 29277
18-08-11 08:18:45    1.2187215674112726
18-08-11 08:18:45 * 13slush
18-08-11 08:18:46 * Pool update done
18-08-11 08:18:46    Type: SCORE
18-08-11 08:18:46    Hash rate: 1862.607 GH/s
18-08-11 08:18:46    Monitoring mode: SHARES
18-08-11 08:18:46    Round shares: 3396962
18-08-11 08:18:46    18.8124296777786
18-08-11 08:18:46 * 14triple
18-08-11 08:18:47 * Pool update done
18-08-11 08:18:47    Type: PROP
18-08-11 08:18:47    Hash rate: 21.29 GH/s
18-08-11 08:18:47    Monitoring mode: SHARES
18-08-11 08:18:47    Round shares: 5508353
18-08-11 08:18:47    7.094266668678551
18-08-11 08:18:47 * 16BitcoinPool
18-08-11 08:18:48 * Pool update done
18-08-11 08:18:48    Type: PROP
18-08-11 08:18:48    Hash rate: 187.59 GH/s
18-08-11 08:18:48    Monitoring mode: TIME
18-08-11 08:18:48    Round time: 36083
18-08-11 08:18:48    2.029729696103863
18-08-11 08:18:48 * 17btcserv
18-08-11 08:18:48 * Pool update done
18-08-11 08:18:48    Type: PROP
18-08-11 08:18:48    Hash rate: 2.605 GH/s
18-08-11 08:18:48    Monitoring mode: SHARES
18-08-11 08:18:48    Round shares: 1109843
18-08-11 08:18:48    1.4293786549929186
18-08-11 08:18:48 * 20Bloodys
18-08-11 08:18:49 * Pool update done
18-08-11 08:18:49    Type: PROP
18-08-11 08:18:49    Hash rate: 0.76 GH/s
18-08-11 08:18:49    Monitoring mode: SHARES
18-08-11 08:18:49    Round shares: 1939241
18-08-11 08:18:49    2.497569198784984
18-08-11 08:18:49 * 24DigBtc
18-08-11 08:18:59 * Socket timeout
* Read timed out
18-08-11 08:18:59 * Update error or pool considered invalid (lagging or down)
18-08-11 08:18:59 * 25NinjaCoin
18-08-11 08:19:00 * Pool update done
18-08-11 08:19:00    Type: PPS
18-08-11 08:19:00    Hash rate: 21.4 GH/s
18-08-11 08:19:00    1.046728971962617
18-08-11 08:19:00 * 26ABCPool
18-08-11 08:19:00 * Pool update done
18-08-11 08:19:00    Type: PPS
18-08-11 08:19:00    Hash rate: 118.0 GH/s
18-08-11 08:19:00    1.0084745762711864
18-08-11 08:19:00 * Most efficient pool is: 5eligius
18-08-11 08:19:00 1.0019985490533871
18-08-11 08:19:00 * Cherry Picking!

[1715020962]

1715020962

[1715020962]

1715020962

[Folax]

Could be, a lot of this above it:

Code:

* 24DigBtc
* Update error or pool considered invalid (lagging or down)
* Most efficient pool is: 5eligius
1.0019877988904107
* Cherry Picking!
================================================================================
[Miner0] 127.0.0.1:8332 18/08/2011 10:41:10, Setting pool bitcoin @  
127.0.0.1:8332
[Miner0] 127.0.0.1:8332 Problems communicating with bitcoin RPC 0 2
[Miner0] 127.0.0.1:8332 Problems communicating with bitcoin RPC 1 2
[Miner0] 127.0.0.1:8332 Problems communicating with bitcoin RPC 2 2
[Miner0] 127.0.0.1:8332 Problems communicating with bitcoin RPC 3 2
[Miner0] 127.0.0.1:8332 18/08/2011 10:41:13, No more backup pools  
left. Using primary and starting over.
[Miner0] 127.0.0.1:8332 18/08/2011 10:41:13, Setting pool bitcoin @  
127.0.0.1:8332
[Miner0] 127.0.0.1:8332 Problems communicating with bitcoin RPC 0 2
[Miner0] 127.0.0.1:8332 Problems communicating with bitcoin RPC 1 2
[Miner0] 127.0.0.1:8332 Problems communicating with bitcoin RPC 2 2
[Miner0] 127.0.0.1:8332 Problems communicating with bitcoin RPC 3 2

Ive read someone else got this 127.0.0.1 problem too (pointing to localhost) but since ive tried 2 Poclbm versions now I don't know what other Poclbm version to try at this point, or if that would solve anything.

[scatterbrain]

Which versions have you tried and are you sure you changed the path cp uses to the new versions you downloaded. I had that issue and resolved it by using m0mchil's poclbm

[Folax]

Is there an easy way to update an existing poclbm install on linux?
Don't want to mess up the whole install by doing it manually step by step.

Does this work?

Code:

wget --no-check-certificate https://github.com/m0mchil/poclbm/raw/master/BitcoinMiner.cl
wget --no-check-certificate https://github.com/m0mchil/poclbm/raw/master/BitcoinMiner.py
wget --no-check-certificate https://github.com/m0mchil/poclbm/raw/master/poclbm.py

-edit- no it doesn't.

[Milkshanks]

been running fast additive_1 for about 2 days now and i noticed that it's picking eligius, a PPS pool, over mtred, a PROP pool which is currently at .094163...this shouldn't be happening should it? i saw this earlier in another situation with bitclockers as well. i'm not getting any errors or anything, it just seems to be prioritizing the PPS pool over the a PROP pool with efficiency way under 1. i changed it to fast additive_2 and it did the same thing. i'll upload the full log for you when i get home bloodred but thought you should know in the meantime. also, no connection issues at all with either pool

Same thing here. Picking Ars instead of 0.08 Mtred. Switching back to normal now.

[Bloodred]

Indeed it should've gone to mtred, it's another bug but I haven't tracked it down yet. Right now, these are the most important things on my to-do list for v0.6.6:

• Fix MULTIPLICATIVE (already done actually)
• Find and fix this new bug Found and fixed it, it was division by 0 (there was only 1 valid prop pool, so maximum hash rate = minimum hash rate)
• Implement configurable error thresholds

I think I may install Linux on my notebook one of these days, so there may be some progress on the Linux front as well.

[Folax]

Would be awesome to get some Linux help. I suspect CP is not the issue but Poclbm is, so it could be a short investigation on your side and great rewards for all of us (greater possible userbase too).
0.2BTC to the person posting the line to update my poclbm install on Linux (Linuxcoin to be exact).

[Bloodred]

CherryPicking has been updated to v0.6.5a
No huge changes this version, a bit of code tidying up and fixed the bugs in the DYNAMIC algorithms (both the one in MULTIPLICATIVE and the one in the 2 ADDITIVE modes). New features coming with 0.6.6, I just released this to get the fixes out, as the bugs were pretty bad.
v0.6.3 to v0.6.5a
v0.6.5 to v0.6.5a

[max in montreal]

i have setup all of the following pools and left the type as is. Are the types correct or should there be some changes?

1bitclockers Type=PROP
2bitcoinlc Type=PROP
3bithasher Type=PROP
4eclipsemc Type=SCORE
5eligius TYPE=BACKUP
7mineco Type=PPLNS
8mtred Type=PROP
9nofee Type=PROP
10ozco Type=PROP
11polmine Type=PROP
13slush Type=SCORE
14triple Type=PROP
15unitedminers Type=PROP
16BitcoinPool Type=PROP
17btcserv Type=PROP
18poolmunity Type=SCORE
19bitp Type=SMPPS
20Bloodys Type=PROP
21BtcMonkey Type=PROP
23BTCWorld Type=PROP

[Bloodred]

Yeah, I believe that's correct.

[amazingrando]

CherryPicking has been updated to v0.6.5a
No huge changes this version, a bit of code tidying up and fixed the bugs in the DYNAMIC algorithms (both the one in MULTIPLICATIVE and the one in the 2 ADDITIVE modes). New features coming with 0.6.6, I just released this to get the fixes out, as the bugs were pretty bad.
v0.6.3 to v0.6.5a
v0.6.5 to v0.6.5a

I use NORMAL, so I haven't checked the other modes, but the upgrade was smooth.  No issues even though I accidentally used the 6.3->6.5a on v6.5.

[Bloodred]

Really? I had no idea bsdiff/bspatch behaved like that. I think you should check the hashes to make sure it's really good though.

[max in montreal]

Yeah, I believe that's correct.

I was just under the impression that we might have to change it to backup manually, as in slush case...

[joker060]

So to use this program you would need to go to every pool listed and sign up, correct?

What kind of % gain are you getting from this program?

[amazingrando]

Really? I had no idea bsdiff/bspatch behaved like that. I think you should check the hashes to make sure it's really good though.

Hashes match.

I think I see the confusion now.  The batch file says

This will update CherryPicking from v0.6.3 to v0.6.5a

So I was confused at which version I was using, but in fact I did use the 6.5->6.5a updater.  It just shows the wrong base version in the batch file (line 2)

[scatterbrain]

thanks for the quick updates. got my rigs going again with dynamic fast multiplicative and everything is working smoothly so far

[marks1976]

I have still been unable to get mtred, rfcpool and bitp to connect using cherry picker.  I am still getting the security messages even after installing the ssl files in the java security folder.

[amazingrando]

I have still been unable to get mtred, rfcpool and bitp to connect using cherry picker.  I am still getting the security messages even after installing the ssl files in the java security folder.

rfcpool is closed, so you don't need to worry about that one.  Bitp.it is SMPPS so you would only use that as a backup.  MtRed is good though, so hopefully you can iron out the issues with that.

Did you try downloading Bloodred's pre-generated jssecacerts file?  Did you put it in C:\Program Files (x86)\Java\jre6\lib\security?

Also, what version of java do you have installed?  32-bit jre6 update 26 works for me.

Good luck

[Folax]

So to use this program you would need to go to every pool listed and sign up, correct?

What kind of % gain are you getting from this program?

I've checked my Mt Red stats and calculated I'm at about 150% efficiency after a week on that pool, didn't bother to check the others but it's good enough for me.

[Bloodred]

So I was confused at which version I was using, but in fact I did use the 6.5->6.5a updater.  It just shows the wrong base version in the batch file (line 2)

I forgot to edit that, oops. The update .bin is definitely good though, yeah.

I have still been unable to get mtred, rfcpool and bitp to connect using cherry picker.  I am still getting the security messages even after installing the ssl files in the java security folder.

Are you sure the jssecacerts file is where it should be (path can differ based on using a 32/64bit OS or 32/64bit JVM)? If you're sure it's in the right place, try reinstalling the JRE.

thanks for the quick updates. got my rigs going again with dynamic fast multiplicative and everything is working smoothly so far

Hope I haven't missed anything serious this time around, but I don't think I have.