Re: Introducing CherryPicking - new Windows & Linux Pool Hopper
Would it be possible that you could implement support for cherry-picking which GPUs we'd like to use for mining? 
Say for instance that I want GPU 0, 1, 3, 4 to be mining with CherryPicking, while GPU 2 is left alone. This can be done with POCLBM and Phoenix, picking which GPU's to dedicate to mining, so could CherryPicking implement this in some way?
EDIT: Anyone else having problems with mainframe, nofee, unitedminers, and bitp.it? CherryPicking has problems connecting to them.
I can implement something like that in the next version, should work well enough.Say for instance that I want GPU 0, 1, 3, 4 to be mining with CherryPicking, while GPU 2 is left alone. This can be done with POCLBM and Phoenix, picking which GPU's to dedicate to mining, so could CherryPicking implement this in some way?
EDIT: Anyone else having problems with mainframe, nofee, unitedminers, and bitp.it? CherryPicking has problems connecting to them.
Also, are the settings for the btcserv configs in the config pack correct? According to btcserv.net, the global network speed was 12.37TH/s, and CherryPicking reports the global speed as 13.7GH/s.. or am I missing something here?
Also, still having issues with mainframe, nofee, unitedminers, and bitp.it.
The global speed is the entire mining network, not just that pool. CherryPicking reports the pools speed, not the network's speed.Great read and very useful info! I'll implement a Score profile where you can set c and that uses the function for the next version of CP.Also, still having issues with mainframe, nofee, unitedminers, and bitp.it.