i just have updated the cuda 7.5 branch after a windows test... no improvements since the RC
I removed all the max limit registers and most of the launchbounds, it helped a bit, but still slower than 6.5
Topic: [ANN] ccminer 2.3 - opensource - GPL (tpruvot) - page 155. (Read 500193 times)
I removed all the max limit registers and most of the launchbounds, it helped a bit, but still slower than 6.5
which one did you test / are failing ?
Is ccminer dropping support for 3.0 cards? Newer versions of the miner don't seem to work, but I also couldn't find anything explicit in readme files.
i just have updated the cuda 7.5 branch after a windows test... no improvements since the RC
Hi tpruvot,
I've seen a ton of commits and that you updated the linux branch, should we switch to it? What are the news?
Thanks a lot!
I've seen a ton of commits and that you updated the linux branch, should we switch to it? What are the news?
Thanks a lot!
Good day all.
Been trying to assemble your latest (ccminer 1.6.6) for a Kepler (GTX 690), (compute 3.5) .
Getting the following error :
'keccak256_cpu_init' at line 299 : invalid device symbol.
Any advice ? Or is it simply a Maxwell only scypt?
Been trying to assemble your latest (ccminer 1.6.6) for a Kepler (GTX 690), (compute 3.5) .
Getting the following error :
'keccak256_cpu_init' at line 299 : invalid device symbol.
Any advice ? Or is it simply a Maxwell only scypt?
you need to add compute 3.5 in the projectfile/makefile.
Good day all.
Been trying to assemble your latest (ccminer 1.6.6) for a Kepler (GTX 690), (compute 3.5) .
Getting the following error :
'keccak256_cpu_init' at line 299 : invalid device symbol.
Any advice ? Or is it simply a Maxwell only scypt?
Been trying to assemble your latest (ccminer 1.6.6) for a Kepler (GTX 690), (compute 3.5) .
Getting the following error :
'keccak256_cpu_init' at line 299 : invalid device symbol.
Any advice ? Or is it simply a Maxwell only scypt?
It's really great to see constant development and open-source engagement in ccminer! Here are some tips for the devs (already sent tip to tpruvot a few days ago):
pallas: https://blockchain.info/tx/538749267db068bb5a0417363087c60f59aba890ed22a3a83d93eab7e73c81ca
sp_ https://blockchain.info/tx/76597bd418e5f8306fe65a9405199a8b7def0327c3ad16e54ac905891c781549
djm34: https://blockchain.info/tx/e33fc9cd80d41c3bcaf2f02c6e60e88647401d600ef4ba633a71dcf043d8e0ff
Keep up the good work and try to keep this project opensource and as much as possible in a single fork - it's much easier for the users this way...
Best regards,
kenshirothefist
pallas: https://blockchain.info/tx/538749267db068bb5a0417363087c60f59aba890ed22a3a83d93eab7e73c81ca
sp_ https://blockchain.info/tx/76597bd418e5f8306fe65a9405199a8b7def0327c3ad16e54ac905891c781549
djm34: https://blockchain.info/tx/e33fc9cd80d41c3bcaf2f02c6e60e88647401d600ef4ba633a71dcf043d8e0ff
Keep up the good work and try to keep this project opensource and as much as possible in a single fork - it's much easier for the users this way...
Best regards,
kenshirothefist
Thanks alot.
A single fork is not that easy since my fork only support compute 5.0 and up devices:
here is the thread:
https://bitcointalksearch.org/topic/ccminersp-mod-modded-nvidia-maxwell-pascal-kernels-826901
1.5.63(sp-MOD) is available here: (31-08-2015)
https://github.com/sp-hash/ccminer/releases/
The sourcecode is available here:
https://github.com/sp-hash/ccminer
It's really great to see constant development and open-source engagement in ccminer! Here are some tips for the devs (already sent tip to tpruvot a few days ago):
pallas: https://blockchain.info/tx/538749267db068bb5a0417363087c60f59aba890ed22a3a83d93eab7e73c81ca
sp_ https://blockchain.info/tx/76597bd418e5f8306fe65a9405199a8b7def0327c3ad16e54ac905891c781549
djm34: https://blockchain.info/tx/e33fc9cd80d41c3bcaf2f02c6e60e88647401d600ef4ba633a71dcf043d8e0ff
Keep up the good work and try to keep this project opensource and as much as possible in a single fork - it's much easier for the users this way...
Best regards,
kenshirothefist
thanks a lot pallas: https://blockchain.info/tx/538749267db068bb5a0417363087c60f59aba890ed22a3a83d93eab7e73c81ca
sp_ https://blockchain.info/tx/76597bd418e5f8306fe65a9405199a8b7def0327c3ad16e54ac905891c781549
djm34: https://blockchain.info/tx/e33fc9cd80d41c3bcaf2f02c6e60e88647401d600ef4ba633a71dcf043d8e0ff
Keep up the good work and try to keep this project opensource and as much as possible in a single fork - it's much easier for the users this way...
Best regards,
kenshirothefist
@epsylon3 per the official websites mining page https://www.dashpay.io/mining/
I downloaded the ccminer optimized for GTX 750 Ti and AVG is picking up that ccminer as a threat "ADP.ARES.Generic"
I want to assume this is a false positive, but figured I'd get some feedback first? Please get back to me.
I downloaded the ccminer optimized for GTX 750 Ti and AVG is picking up that ccminer as a threat "ADP.ARES.Generic"
I want to assume this is a false positive, but figured I'd get some feedback first? Please get back to me.
It's really great to see constant development and open-source engagement in ccminer! Here are some tips for the devs (already sent tip to tpruvot a few days ago):
pallas: https://blockchain.info/tx/538749267db068bb5a0417363087c60f59aba890ed22a3a83d93eab7e73c81ca
sp_ https://blockchain.info/tx/76597bd418e5f8306fe65a9405199a8b7def0327c3ad16e54ac905891c781549
djm34: https://blockchain.info/tx/e33fc9cd80d41c3bcaf2f02c6e60e88647401d600ef4ba633a71dcf043d8e0ff
Keep up the good work and try to keep this project opensource and as much as possible in a single fork - it's much easier for the users this way...
Best regards,
kenshirothefist
pallas: https://blockchain.info/tx/538749267db068bb5a0417363087c60f59aba890ed22a3a83d93eab7e73c81ca
sp_ https://blockchain.info/tx/76597bd418e5f8306fe65a9405199a8b7def0327c3ad16e54ac905891c781549
djm34: https://blockchain.info/tx/e33fc9cd80d41c3bcaf2f02c6e60e88647401d600ef4ba633a71dcf043d8e0ff
Keep up the good work and try to keep this project opensource and as much as possible in a single fork - it's much easier for the users this way...
Best regards,
kenshirothefist
Thanks, much appreciated! :-)
It's really great to see constant development and open-source engagement in ccminer! Here are some tips for the devs (already sent tip to tpruvot a few days ago):
pallas: https://blockchain.info/tx/538749267db068bb5a0417363087c60f59aba890ed22a3a83d93eab7e73c81ca
sp_ https://blockchain.info/tx/76597bd418e5f8306fe65a9405199a8b7def0327c3ad16e54ac905891c781549
djm34: https://blockchain.info/tx/e33fc9cd80d41c3bcaf2f02c6e60e88647401d600ef4ba633a71dcf043d8e0ff
Keep up the good work and try to keep this project opensource and as much as possible in a single fork - it's much easier for the users this way...
Best regards,
kenshirothefist
pallas: https://blockchain.info/tx/538749267db068bb5a0417363087c60f59aba890ed22a3a83d93eab7e73c81ca
sp_ https://blockchain.info/tx/76597bd418e5f8306fe65a9405199a8b7def0327c3ad16e54ac905891c781549
djm34: https://blockchain.info/tx/e33fc9cd80d41c3bcaf2f02c6e60e88647401d600ef4ba633a71dcf043d8e0ff
Keep up the good work and try to keep this project opensource and as much as possible in a single fork - it's much easier for the users this way...
Best regards,
kenshirothefist
sp work is not always easy to reuse, i mostly search the best performance on linux and that doesnt always match with windows :p
But i can generally reuse a part of its work, or at least i can see where there are rooms of improvement.
I recently tried the most profitable algos (quark, x11, neoscrypt) in your fork compared to sp_'s and they are significantly slower.But i can generally reuse a part of its work, or at least i can see where there are rooms of improvement.
I mine on linux only, with compute 5.2 cards and cuda 6.5.
I made the latest 10% enhancement over his neoscrypt kernel (which is actually djm34 code): I think you can safely use it on your fork, the only caveat is that it doesn't include compute <5.0 code.
It's DJM34's code with modding. 7-10% faster than the first opensource version. You added another 10% so then it's 20% faster than the first version. If people choose to publish their work, other people will help to make it faster. I prefer opensource, but I understand why people keep it private.
Here is my first improvement (neoscrypt +7%):
https://github.com/sp-hash/ccminer/commit/48072790339fc021f096e20765ed8cd03701c155
sp work is not always easy to reuse, i mostly search the best performance on linux and that doesnt always match with windows :p
But i can generally reuse a part of its work, or at least i can see where there are rooms of improvement.
But i can generally reuse a part of its work, or at least i can see where there are rooms of improvement.
I recently tried the most profitable algos (quark, x11, neoscrypt) in your fork compared to sp_'s and they are significantly slower.
I mine on linux only, with compute 5.2 cards and cuda 6.5.
I made the latest 10% enhancement over his neoscrypt kernel (which is actually djm34 code): I think you can safely use it on your fork, the only caveat is that it doesn't include compute <5.0 code.
sp work is not always easy to reuse, i mostly search the best performance on linux and that doesnt always match with windows :p
But i can generally reuse a part of its work, or at least i can see where there are rooms of improvement.
But i can generally reuse a part of its work, or at least i can see where there are rooms of improvement.
tpruvot ccminer with sp_ hashrates would be a dream come true :-)
actually it wouldn't be impossible if we find a way to work together and get some donations in the process...
maybe Chrysophylax donation links and multipool is the way.
actually it wouldn't be impossible if we find a way to work together and get some donations in the process...
maybe Chrysophylax donation links and multipool is the way.
v1.6.6 released : https://github.com/tpruvot/ccminer/releases/tag/1.6.6-tpruvot
tpruvot, thanks for the new release, it is really good to see always up-to-date ccminer development and releases! Here is a small 0.1 BTC tip for you: https://blockchain.info/tx/669606aff5c01f9da376384a61d9871b5704f4eb52c4c2d885e6611b05d4e6ed
And keep up the good work (I wish that there would be someone who would also keep sgminer as much up to date as ccminer is
).Thanks.. Really appreciated
Lyra2 v2 will be improved when i will have a bit more of free time..
Superb work once again!
I did notice though,that the DJM edition performs up to 500 KH/s better for the Lyra2v2 algo...on 780Ti's with identical intensity set(20)
I did notice though,that the DJM edition performs up to 500 KH/s better for the Lyra2v2 algo...on 780Ti's with identical intensity set(20)
v1.6.6 released : https://github.com/tpruvot/ccminer/releases/tag/1.6.6-tpruvot
tpruvot, thanks for the new release, it is really good to see always up-to-date ccminer development and releases! Here is a small 0.1 BTC tip for you: https://blockchain.info/tx/669606aff5c01f9da376384a61d9871b5704f4eb52c4c2d885e6611b05d4e6ed
And keep up the good work (I wish that there would be someone who would also keep sgminer as much up to date as ccminer is
). Jump to: