chrysophylax
Legendary
Offline
Activity: 2828
Merit: 1091
--- ChainWorks Industries ---
|
|
May 20, 2015, 06:44:02 AM |
|
sp ...
just out of curiosity - will you implement blake2b algo in ccminer? ...
ive been seeing a number of chats about the algo - which usually leads to new coins being created to make use of the algo ...
#crysx
|
|
|
|
Epsylon3
Legendary
Offline
Activity: 1484
Merit: 1082
ccminer/cpuminer developer
|
|
May 20, 2015, 07:01:53 AM |
|
else.. on the other branch... multi pools config and pool failover/time switching is almost ready.
I can say it will be in my next release.. 1.6.4
|
|
|
|
sp_ (OP)
Legendary
Offline
Activity: 2912
Merit: 1087
Team Black developer
|
|
May 20, 2015, 07:19:55 AM Last edit: May 20, 2015, 07:36:16 AM by sp_ |
|
sp ... just out of curiosity - will you implement blake2b algo in ccminer? ... ive been seeing a number of chats about the algo - which usually leads to new coins being created to make use of the algo ... #crysx
Writing it in before there's a PoW using it is a waste of time; additionally, it's already there - Neoscrypt uses Blake2b, I believe. I have already optimized the blake implementation in Neoscrypt (from djm34's version). the total hashgain was around 7% on the 750ti. So the latest Sp-mod is around 7% faster than the optimized djm34 version when mining neoscrypt.
|
|
|
|
Grout
|
|
May 20, 2015, 02:02:40 PM |
|
This is SP_artaaaa!! well this is a Marathon to try to explain to new comers to crypto than there is a little more to crypto than just plugging their card to a pool and expecting money... it is called mining not milking... so there is some prospection involved... Just started a dedicated thread so we can stop hijacking SP's with this discussion: https://bitcointalk.org/index.php?topic=1066450.0
|
|
|
|
fenomenhaa
|
|
May 20, 2015, 03:47:59 PM |
|
This is SP_artaaaa!! well this is a Marathon to try to explain to new comers to crypto than there is a little more to crypto than just plugging their card to a pool and expecting money... it is called mining not milking... so there is some prospection involved... Just started a dedicated thread so we can stop hijacking SP's with this discussion: https://bitcointalk.org/index.php?topic=1066450.0At last !!! )) enough for offtopic discussions ))) .@Sp At this time is there any update )))
|
▄▄█▄█▄[/color] ▄▀▀▀▄ ██ ██ ▄▀▀▀▄ █ █▀▀[color=#2C97
|
|
|
joblo
Legendary
Offline
Activity: 1470
Merit: 1114
|
|
May 20, 2015, 11:44:02 PM Last edit: May 21, 2015, 02:57:22 AM by joblo |
|
I noticed the following error a couple of times while mining quark at westhash with ccminer 1.5.50-SP, default parameters, seen on both Linux and Windows. I don't know if it's the same reject reason everytime but it's always the first share submitted after the stratum set nonce. They seem to be very rare.
[2015-05-20 18:04:02] GPU #0: GeForce GTX 970, 15904 [2015-05-20 18:04:02] accepted: 6820/6863 (99.37%), 27426 khash/s yay!!! [2015-05-20 18:04:03] GPU #1: GeForce GTX 780 Ti, 11438 [2015-05-20 18:04:03] accepted: 6821/6864 (99.37%), 27426 khash/s yay!!! [2015-05-20 18:04:04] Stratum set nonce 77ffffc2f2 with extranonce2 size=3 [2015-05-20 18:04:14] GPU #0: GeForce GTX 970, 15922 [2015-05-20 18:04:14] accepted: 6821/6865 (99.36%), 27425 khash/s booooo [2015-05-20 18:04:14] reject reason: Share above target. [2015-05-20 18:04:16] stratum.westhash.com:3345 quark block 1678360 [2015-05-20 18:04:16] GPU #1: GeForce GTX 780 Ti, 11475 [2015-05-20 18:04:16] GPU #0: GeForce GTX 970, 16062 [2015-05-20 18:04:17] GPU #1: GeForce GTX 780 Ti, 11450 [2015-05-20 18:04:18] accepted: 6822/6866 (99.36%), 27416 khash/s yay!!
I also get an initial retry message when connecting to the same pool, most of the time but not every time. It always connects after the timeout. It's odd because there is no associated error message, just the retry message and the 30 second wait. Again seen on both Linux and Windows.
I don't know if they are related or are related to the CTRL-C crash but they all seem to be recent regressions. Seems more likely they would be related to tpruvot's changes that SP's.
Edit: I don't recall ever seeing the first error on yaamp. I khow the second error did not occur on yaamp. The CTRL-C crash occurs every time anywhere.
Any thoughts?
Update: a rejected share does not occur every time there is a stratum set nonce. I have also seen job not found following stratum set nonce
|
|
|
|
chrysophylax
Legendary
Offline
Activity: 2828
Merit: 1091
--- ChainWorks Industries ---
|
|
May 21, 2015, 03:16:32 AM |
|
sp ... just out of curiosity - will you implement blake2b algo in ccminer? ... ive been seeing a number of chats about the algo - which usually leads to new coins being created to make use of the algo ... #crysx
Writing it in before there's a PoW using it is a waste of time; additionally, it's already there - Neoscrypt uses Blake2b, I believe. I have already optimized the blake implementation in Neoscrypt (from djm34's version). the total hashgain was around 7% on the 750ti. So the latest Sp-mod is around 7% faster than the optimized djm34 version when mining neoscrypt. kool ... i asked due to the chat about some new coins that will be coming out with blake2b algo - specifically looking at sia ... its better to be ready for the coins than wait till they come out and scramble to try and get in before the major players do ... thats all im saying ... so even if it a simple non-optimized implementation - its better than not having it ... but if the -a blake option will process blake2b - then is all good ... thought id ask - thats all ... you guys are the experts with this ... #crysx
|
|
|
|
chrysophylax
Legendary
Offline
Activity: 2828
Merit: 1091
--- ChainWorks Industries ---
|
|
May 21, 2015, 03:18:58 AM |
|
I noticed the following error a couple of times while mining quark at westhash with ccminer 1.5.50-SP, default parameters, seen on both Linux and Windows. I don't know if it's the same reject reason everytime but it's always the first share submitted after the stratum set nonce. They seem to be very rare.
[2015-05-20 18:04:02] GPU #0: GeForce GTX 970, 15904 [2015-05-20 18:04:02] accepted: 6820/6863 (99.37%), 27426 khash/s yay!!! [2015-05-20 18:04:03] GPU #1: GeForce GTX 780 Ti, 11438 [2015-05-20 18:04:03] accepted: 6821/6864 (99.37%), 27426 khash/s yay!!! [2015-05-20 18:04:04] Stratum set nonce 77ffffc2f2 with extranonce2 size=3 [2015-05-20 18:04:14] GPU #0: GeForce GTX 970, 15922 [2015-05-20 18:04:14] accepted: 6821/6865 (99.36%), 27425 khash/s booooo [2015-05-20 18:04:14] reject reason: Share above target. [2015-05-20 18:04:16] stratum.westhash.com:3345 quark block 1678360 [2015-05-20 18:04:16] GPU #1: GeForce GTX 780 Ti, 11475 [2015-05-20 18:04:16] GPU #0: GeForce GTX 970, 16062 [2015-05-20 18:04:17] GPU #1: GeForce GTX 780 Ti, 11450 [2015-05-20 18:04:18] accepted: 6822/6866 (99.36%), 27416 khash/s yay!!
I also get an initial retry message when connecting to the same pool, most of the time but not every time. It always connects after the timeout. It's odd because there is no associated error message, just the retry message and the 30 second wait. Again seen on both Linux and Windows.
I don't know if they are related or are related to the CTRL-C crash but they all seem to be recent regressions. Seems more likely they would be related to tpruvot's changes that SP's.
Edit: I don't recall ever seeing the first error on yaamp. I khow the second error did not occur on yaamp. The CTRL-C crash occurs every time anywhere.
Any thoughts?
Update: a rejected share does not occur every time there is a stratum set nonce. I have also seen job not found following stratum set nonce
we get that here too ... but i think its more a pool issue than miner ... i could very easily be mistaken ... not a major issue though - especially if it stays on mining well ... ive seen 'job not found' and other rejected share reasons with a few algos also ... btw - nice hashes on the cards ... #crysx
|
|
|
|
joblo
Legendary
Offline
Activity: 1470
Merit: 1114
|
|
May 21, 2015, 04:49:21 AM |
|
I noticed the following error a couple of times while mining quark at westhash with ccminer 1.5.50-SP, default parameters, seen on both Linux and Windows. I don't know if it's the same reject reason everytime but it's always the first share submitted after the stratum set nonce. They seem to be very rare.
[2015-05-20 18:04:02] GPU #0: GeForce GTX 970, 15904 [2015-05-20 18:04:02] accepted: 6820/6863 (99.37%), 27426 khash/s yay!!! [2015-05-20 18:04:03] GPU #1: GeForce GTX 780 Ti, 11438 [2015-05-20 18:04:03] accepted: 6821/6864 (99.37%), 27426 khash/s yay!!! [2015-05-20 18:04:04] Stratum set nonce 77ffffc2f2 with extranonce2 size=3 [2015-05-20 18:04:14] GPU #0: GeForce GTX 970, 15922 [2015-05-20 18:04:14] accepted: 6821/6865 (99.36%), 27425 khash/s booooo [2015-05-20 18:04:14] reject reason: Share above target. [2015-05-20 18:04:16] stratum.westhash.com:3345 quark block 1678360 [2015-05-20 18:04:16] GPU #1: GeForce GTX 780 Ti, 11475 [2015-05-20 18:04:16] GPU #0: GeForce GTX 970, 16062 [2015-05-20 18:04:17] GPU #1: GeForce GTX 780 Ti, 11450 [2015-05-20 18:04:18] accepted: 6822/6866 (99.36%), 27416 khash/s yay!!
I also get an initial retry message when connecting to the same pool, most of the time but not every time. It always connects after the timeout. It's odd because there is no associated error message, just the retry message and the 30 second wait. Again seen on both Linux and Windows.
I don't know if they are related or are related to the CTRL-C crash but they all seem to be recent regressions. Seems more likely they would be related to tpruvot's changes that SP's.
Edit: I don't recall ever seeing the first error on yaamp. I khow the second error did not occur on yaamp. The CTRL-C crash occurs every time anywhere.
Any thoughts?
Update: a rejected share does not occur every time there is a stratum set nonce. I have also seen job not found following stratum set nonce
we get that here too ... but i think its more a pool issue than miner ... i could very easily be mistaken ... not a major issue though - especially if it stays on mining well ... ive seen 'job not found' and other rejected share reasons with a few algos also ... btw - nice hashes on the cards ... #crysx Agreed, not a major issue and likely a pool issue. Just noticed the pattern and thought I'd mention it. The cards are EVGAs, OCed at the factory but not by me. Thanks.
|
|
|
|
sp_ (OP)
Legendary
Offline
Activity: 2912
Merit: 1087
Team Black developer
|
|
May 21, 2015, 07:03:34 AM |
|
In my fork of ccminer I Submit stale shares. This was because the hashrate on some pools dropped alot if I didn't do this. If you are on a slow connection, this might leed to a higher reject rate.
I will make an option for submit stale shares like we have in sgminer..
|
|
|
|
Epsylon3
Legendary
Offline
Activity: 1484
Merit: 1082
ccminer/cpuminer developer
|
|
May 21, 2015, 08:10:12 AM |
|
Yes could be a thread lock issue... I try to fix this kind of problems since months...
Some other problems seems to be on the pool... Not easy to fix that for all the possible cases.
|
|
|
|
pallas
Legendary
Offline
Activity: 2716
Merit: 1094
Black Belt Developer
|
|
May 21, 2015, 01:24:00 PM |
|
did some optimization on quark: +75% (roughly) yeah... well 10 Mh/s on 750Ti?? That's really great!! will you merge the mods, make a new repo or sell it?
|
|
|
|
rednoW
Legendary
Offline
Activity: 1510
Merit: 1003
|
|
May 21, 2015, 01:31:58 PM |
|
10 Mh/s on 750Ti?? That's really great!! will you merge the mods, make a new repo or sell it?
duplicate share dirty trick. Let's ban him
|
|
|
|
CapnBDL
|
|
May 21, 2015, 03:34:43 PM |
|
did some optimization on quark: +75% (roughly) yeah... well 10 Mh/s on 750Ti?? That's really great!! will you merge the mods, make a new repo or sell it? WHAT? 10Mh /w a 750Ti mining quark? Best I get is just under 6.5. No way...unbelievable. Almost speechless.
|
|
|
|
sp_ (OP)
Legendary
Offline
Activity: 2912
Merit: 1087
Team Black developer
|
|
May 21, 2015, 03:39:33 PM |
|
I just tested the uppercase hack on nicehash. Seems to not work... I submit a share, then I change some of the casing and submit again.. https://bitcointalk.org/index.php?topic=1065576.0
|
|
|
|
djm34
Legendary
Offline
Activity: 1400
Merit: 1050
|
|
May 21, 2015, 05:34:21 PM |
|
did some optimization on quark: +75% (roughly) yeah... well 10 Mh/s on 750Ti?? That's really great!! will you merge the mods, make a new repo or sell it? well... that was a bug it is rather +1MH/s for 980/780 and 0.5MH/s for the 750ti
|
djm34 facebook pageBTC: 1NENYmxwZGHsKFmyjTc5WferTn5VTFb7Ze Pledge for neoscrypt ccminer to that address: 16UoC4DmTz2pvhFvcfTQrzkPTrXkWijzXw
|
|
|
sp_ (OP)
Legendary
Offline
Activity: 2912
Merit: 1087
Team Black developer
|
|
May 21, 2015, 06:09:59 PM |
|
did some optimization on quark: +75% (roughly) yeah... well 10 Mh/s on 750Ti?? That's really great!! will you merge the mods, make a new repo or sell it? well... that was a bug it is rather +1MH/s for 980/780 and 0.5MH/s for the 750ti Pretty good. I see some optimalizations as well.
|
|
|
|
CapnBDL
|
|
May 21, 2015, 08:37:21 PM |
|
Hey Folks....I know this isn't the right place, but quick question......how do I launch ccminer to solo mine a coin. I know it's a .bat but .... what?
Yeah...I know...newbs question, except, I've never actually tried to solo. I know the p2p & rcp ports. Brand new coin I wanna try mining before it hits 5000 blocks, at 1700 right now, so low diff. Just curious.
|
|
|
|
5w00p
|
|
May 21, 2015, 08:46:44 PM |
|
Hey Folks....I know this isn't the right place, but quick question......how do I launch ccminer to solo mine a coin. I know it's a .bat but .... what?
Yeah...I know...newbs question, except, I've never actually tried to solo. I know the p2p & rcp ports.
AFAIK, you can't actually solomine with ccminer. The work-around is that you would have to create your own pool, then point your workers at it. It would reside in your local network, or even at the loopback address (127.0.0.1)
|
|
|
|
CapnBDL
|
|
May 21, 2015, 09:12:08 PM |
|
Hey Folks....I know this isn't the right place, but quick question......how do I launch ccminer to solo mine a coin. I know it's a .bat but .... what?
Yeah...I know...newbs question, except, I've never actually tried to solo. I know the p2p & rcp ports.
AFAIK, you can't actually solomine with ccminer. The work-around is that you would have to create your own pool, then point your workers at it. It would reside in your local network, or even at the loopback address (127.0.0.1) Not nice man....if 61 is a kid. No need to be rude. I said I've never solo mined. Tough crowd. Just trying to learn.
|
|
|
|
|