Topic: Introducing CherryPicking - new Windows & Linux Pool Hopper - page 13. (Read 43136 times)
Have you been running without a PPS/BACKUP pool for that week? That could definitely decrease efficiency. If not, have a look through the logs/stats to see if there were invalid hops or something. Also, what hopping algorithm are you using?
Ok, I will add ars back in.
What would the cfg be for this pool?
http://simplecoin.us/index.php
Thanks.
EDIT:
So I have been running CP for about 7 days now, and it seems like I have only made about 3 - 3.5 BTC on 950-1000 MHash/s. That seems low to me. What am I doing wrong/What are other people making with that speed?
What would the cfg be for this pool?
http://simplecoin.us/index.php
Thanks.
EDIT:
So I have been running CP for about 7 days now, and it seems like I have only made about 3 - 3.5 BTC on 950-1000 MHash/s. That seems low to me. What am I doing wrong/What are other people making with that speed?
You need 1 PPS pool for proper operation. Good hopping is not guaranteed if you do not have at least 1 PPS pool.
What other pools would be good to add here? I don't want to use PPS pools.
1bitclockers
2bitcoinlc
3bithasher
4eclipsemc
7mineco
8mtred
9nofee
10ozco
11polmine
13slush
14triple
15unitedminers
16BitcoinPool
17btcserv
19bitp
20bloodys
22BTCPool24
24DigBtc
26ABCPool
1bitclockers
2bitcoinlc
3bithasher
4eclipsemc
7mineco
8mtred
9nofee
10ozco
11polmine
13slush
14triple
15unitedminers
16BitcoinPool
17btcserv
19bitp
20bloodys
22BTCPool24
24DigBtc
26ABCPool
@wtfman Sorry for posting the web scrape cfg, it was late at night when I wrote that post and accidentally opened the wrong one. So, everyone can safely use the JSON .cfg for btcserv, it's in the archive and should work fine. Remember to NOT have both of them active in CherryPicking, they are provided as alternative options.
I wouldn't even bother with poolmunity... The owner sent out an email saying he was closing the pool on the 1st of September since he wasn't getting any traffic.
Is anyone else having trouble with poolmunity? It has been getting the lagging/time-out error for me.
So, I've checked the pools out.
unitedminers seems to have flaky at best performance, there's something wrong on their side (lots of network timeouts and such). Not much I can do about that.
BitcoinPool works for me with the exact same .cfg from the archive, are you sure you haven't changed/deleted something by accident?
btcserv have changed their hash rate display from MHash/s to GHash/s, here is the new .cfg (will be added to the archive but just copy-paste the content for the time being):
unitedminers seems to have flaky at best performance, there's something wrong on their side (lots of network timeouts and such). Not much I can do about that.
BitcoinPool works for me with the exact same .cfg from the archive, are you sure you haven't changed/deleted something by accident?
btcserv have changed their hash rate display from MHash/s to GHash/s, here is the new .cfg (will be added to the archive but just copy-paste the content for the time being):
Code:
;BTCSERV
;Home Page: http:/btcserv.net
Type=PROP
Host=btcserv.net
Port=8335
JSON=http://btcserv.net
HashEx1=[ \.0-9]+GHash/s
HashEx2=[ \.0-9]+
HashRemove=
SharesEx1=[ ,0-9]+shares
SharesEx2=[ ,0-9]+
SharesRemove= ,
Div=1
;Home Page: http:/btcserv.net
Type=PROP
Host=btcserv.net
Port=8335
JSON=http://btcserv.net
HashEx1=[ \.0-9]+GHash/s
HashEx2=[ \.0-9]+
HashRemove=
SharesEx1=[ ,0-9]+shares
SharesEx2=[ ,0-9]+
SharesRemove= ,
Div=1
hey,
i am the operator of btcserv.net and wanted to let you know that now json stats are available @ http://btcserv.net/json/pool/ .. would be cool if dev team could update/add whatever necessary so the data is fetched from there.
greetings.
i am the operator of btcserv.net and wanted to let you know that now json stats are available @ http://btcserv.net/json/pool/ .. would be cool if dev team could update/add whatever necessary so the data is fetched from there.
greetings.
What about LowCost? They seem to be delaying their stats or something, since CP always start mining on it around 0.8 or something like that.
I changed/updated my nofee .cfg a few days ago and it worked fine for about a day before the errors started again so maybe it will clear up...
So, I've checked the pools out.
unitedminers seems to have flaky at best performance, there's something wrong on their side (lots of network timeouts and such). Not much I can do about that.
BitcoinPool works for me with the exact same .cfg from the archive, are you sure you haven't changed/deleted something by accident?
btcserv have changed their hash rate display from MHash/s to GHash/s, here is the new .cfg (will be added to the archive but just copy-paste the content for the time being). Note that there is a JSON .cfg available for btcserv as well, which you should use if it works well for you as it causes much, much less unneeded traffic for the server. This is simply provided as an alternative:
nofee have both changed their URL and seem to be doing shady stuff with the statistics, namely randomly reporting hash rates of 0 which makes CherryPicking consider the pool invalid (mining on a pool where you're the only miner is solo mining and cannot bring you any profit). I don't know if this is an error on their end or intentional in order to mess with hoppers, in any case we have to wait a few days to see if it clears up, if not I'll see if there's something I could do to bypass their limitations. Here's the .cfg that accounts for the URL change:
unitedminers seems to have flaky at best performance, there's something wrong on their side (lots of network timeouts and such). Not much I can do about that.
BitcoinPool works for me with the exact same .cfg from the archive, are you sure you haven't changed/deleted something by accident?
btcserv have changed their hash rate display from MHash/s to GHash/s, here is the new .cfg (will be added to the archive but just copy-paste the content for the time being). Note that there is a JSON .cfg available for btcserv as well, which you should use if it works well for you as it causes much, much less unneeded traffic for the server. This is simply provided as an alternative:
Code:
;BTCSERV
;Home Page: http:/btcserv.net
Type=PROP
Host=btcserv.net
Port=8335
JSON=http://btcserv.net
HashEx1=[ \.0-9]+GHash/s
HashEx2=[ \.0-9]+
HashRemove=
SharesEx1=[ ,0-9]+shares
SharesEx2=[ ,0-9]+
SharesRemove= ,
Div=1
;Home Page: http:/btcserv.net
Type=PROP
Host=btcserv.net
Port=8335
JSON=http://btcserv.net
HashEx1=[ \.0-9]+GHash/s
HashEx2=[ \.0-9]+
HashRemove=
SharesEx1=[ ,0-9]+shares
SharesEx2=[ ,0-9]+
SharesRemove= ,
Div=1
nofee have both changed their URL and seem to be doing shady stuff with the statistics, namely randomly reporting hash rates of 0 which makes CherryPicking consider the pool invalid (mining on a pool where you're the only miner is solo mining and cannot bring you any profit). I don't know if this is an error on their end or intentional in order to mess with hoppers, in any case we have to wait a few days to see if it clears up, if not I'll see if there's something I could do to bypass their limitations. Here's the .cfg that accounts for the URL change:
Code:
;NoFeeMining.com
Type=PROP
Host=nofeemining.appspot.com
Port=8332
JSON=http://nofeemining.appspot.com/api.php
HashEx1="poolspeed":\d+\.?\d*
HashEx2=\d+\.?\d*
SharesEx1="poolRoundShares":\d+
SharesEx2=\d+
Div=1
Type=PROP
Host=nofeemining.appspot.com
Port=8332
JSON=http://nofeemining.appspot.com/api.php
HashEx1="poolspeed":\d+\.?\d*
HashEx2=\d+\.?\d*
SharesEx1="poolRoundShares":\d+
SharesEx2=\d+
Div=1
im using your cfg zip but these 4 pools dont seem to work but i can get to them by the website.
* 15unitedminers
* Update error or pool considered invalid (lagging or down)
* 16BitcoinPool
* Update error or pool considered invalid (lagging or down)
* 17btcserv
* Update error or pool considered invalid (lagging or down)
* 9nofee
* Update error or pool considered invalid (lagging or down)
* 15unitedminers
* Update error or pool considered invalid (lagging or down)
* 16BitcoinPool
* Update error or pool considered invalid (lagging or down)
* 17btcserv
* Update error or pool considered invalid (lagging or down)
* 9nofee
* Update error or pool considered invalid (lagging or down)
When I added Device=0,1 to use both my cards, it says "0,1 is not a number, using 0".
What am I doing wrong here?
That only tells CherryPicking what device to start mining with and really has no use if your GPUs start with device 0. It's only useful if your CPU is identified as device 0. To add more GPUs, add a Miner= line in each pool .cfg for each GPU with the required mining credentials to mine on that pool. CherryPicking will use as many GPUs as there are valid Miner= lines. Note that I highly recommend having the same number of Miner lines in all your pool .cfg files. What am I doing wrong here?
You only need to put device=0. It will use any gpu starting with 0 and going up to however many gpus you have. You don't need to explicity tell it to use anything. Leaving it blank at device= will default to 0 anyway
When I added Device=0,1 to use both my cards, it says "0,1 is not a number, using 0".
What am I doing wrong here?
What am I doing wrong here?
From the read me:
Device - a number which tells the hopper which device it should start mining with. Default is 0 and you probably only need to change it to 1 if poclbm sees your CPU as device 0.
I don't even use that argument... in my settings I just have:
;Device=
and it works fine. Try it like that or with Device=0 and see if all your cards are working.
When I added Device=0,1 to use both my cards, it says "0,1 is not a number, using 0".
What am I doing wrong here?
What am I doing wrong here?
Java can't do that, but on Windows 7 you can use the start command to force affinity. I'll upload some .bat files shortly.
OK, I got it kinda got it working using the start command with the start w/ logging bat. It's setting the affinity but logging isn't working. I have no idea what I'm doing... lol so hopefully you can come up with one that works.
Code:
@echo off
start /affinity 1 java -jar CherryPicking.jar -logging -stats
exit
This should force affinity to CPU0. Note that 1 isn't the CPU number, it's a bitmask.start /affinity 1 java -jar CherryPicking.jar -logging -stats
exit
Thanks Bloodred! It works perfectly.
Java can't do that, but on Windows 7 you can use the start command to force affinity. I'll upload some .bat files shortly.
OK, I got it kinda got it working using the start command with the start w/ logging bat. It's setting the affinity but logging isn't working. I have no idea what I'm doing... lol so hopefully you can come up with one that works.
Code:
@echo off
start /affinity 1 java -jar CherryPicking.jar -logging -stats
exit
This should force affinity to CPU0. Note that 1 isn't the CPU number, it's a bitmask. start /affinity 1 java -jar CherryPicking.jar -logging -stats
exit
it sounds like you removed the code to tell CP to use all 3 of your gpu's. each gpu needs a miner= line in the cfg file for CP to use it. what exactly did removing the other 2 fix for you? the connection issue with mtred is unrelated to how many gpu's you use
Lol i figured it out was a mistake on me when i made the 3rd acount on mtred i had a typo.
Java can't do that, but on Windows 7 you can use the start command to force affinity. I'll upload some .bat files shortly.
OK, I got it kinda got it working using the start command with the start w/ logging bat. It's setting the affinity but logging isn't working. I have no idea what I'm doing... lol so hopefully you can come up with one that works.
Jump to: