CCminer(SP-MOD) Modded GPU kernels.

[pallas]

I've found a solution to the neoscrypt problem: building a cuda 6.5/7.5 hybrid.

This is not a solution, this is a workaround.

I don't see a problem.
Most people already have both cuda 6.5 and 7.5.
With some little changes to the Makefile, you could compile each kernel with its best cuda version, in a single executable.

PLEASE POST THE FRANKEN-WEENIE WORKAROUND--

If you could post a Windows executable with the promised features, I'll donate.  Quark is faster with release dot 76.  I want to use the executable with NiceHash Miner and auto-switch.  On Linux, I could compile it myself... but I don't have a working autoswitch script.       --scryptr

I never built ccminer on windows. I don't even have a working windows environment with cuda and nvidia drivers. Sorry.
Maybe I could do a Makefile (or whatever) patch to make neoscrypt compile on 6.5 and post a pull request? That way sp_ can build the win binary for everybody. But I don't think he agrees on "the method".

[sp_]

Got the test results on a EVGA 980 reference standard clocks.
                 76-7.5       76-6.5        74-6.5    74-7.5
quark        19.9          19.3           19.3        19.7
x11           9850         9920          10000     7680
lyra2v2     10.7          11.4           11.6        10.9
neo           220           635            640         220

Thanks for testing. Can you please try to compile release 74 with x86 build and cuda 7.5?

Done, results included above. The quark rate with 74-7.5 was unexpected, some of the previous changes
must have provided a bigger improvement on cuda 7.5 than 6.5

My tuning rig doesn't contain a gtx 980. I only have 750ti, 960, 970x2. your results are different than mine in the quark algo.

As you can see I have optimized x11 30% faster(than release 74 compiled with cuda 7.5), but still slower than cuda 6.5.


(but only 4 of the 11 x11 kernals have been changed)

[scryptr]

MINERS WILL DONATE FOR FRANKEN-WEENIE--

No waiting. Work on the purist executable at your own pace.  Maybe DJM will flip out some useful code for neoscrypt.  Maybe we will all just get along.       --scryptr

[joblo]

I've found a solution to the neoscrypt problem: building a cuda 6.5/7.5 hybrid.
Tested working on Linux. Here's the procedure:

- build ccminer with cuda 7.5 as usual
- remove all the object files in the neoscrypt folder: rm neoscrypt/*.o
- edit Makefile
- replace all the instances of "7.5" with "6.5"
- run make again
- you just made a ccminer executable with all the algos on 7.5 except neoscrypt on 6.5 :-)
- revert the Makefile changes to build it again in the future

If you find this useful, please donate to the BTC address in my signature.

If I undertstand the result neo is compiled with 6.5 and eveyrthing else with 7.5. Then it is all linked
with 6.5. I'm not sure linking object files from different compilers is safe.

I prefer to use a script to select the prefered executable based on the algo. Less work, less risk, more
flexible.

Edit: but it's still a workaround.

Linking object files from different compilers: I've often linked object files create with a C compiler and others created with an assembler.
In ccminer, some objects are compiled with gcc, some others with nvcc... you get the picture.

I get the picture. I got a pascal program to call a fortran subroutine several decades ago. No available linker could handle it I had to
link it manually.

The examples you gave are where it is explicitly supported by the respective linkers. I wouldn't expect that support in different
major versions of the same compiler. ABI changes can be introduced.

I'm not saying it can't be done, just that it's probably not supported and might not always work.

used for quite some time c++ programme linked to old fortran libraries, this was done automatically (well in a script).

Also regarding nvcc, there are different way to link and compile. You can very well compile one part or the other with one cuda version or another and do the linking with gcc (and I am not entirely sure, but I think for linking cuda is just calling the default compiler (gcc or visual stuff... so actually it doesn't really matter that you compile with various cuda version...

Just for kicks I googled it. nvcc does do a compatibility check on g++ (in the example below) versions so they do explicitly support
it and there are versions that don't work.

http://stackoverflow.com/questions/9421108/how-can-i-compile-cuda-code-then-link-it-to-a-c-project

I don't know for sure whether nvcc supports different versions of itself, it may have checked and passed in your case.
If I was a compiler developper it would be a very low priority as it would complicate changing the ABI and is generally only useful
when the original source code is not available.

[djm34]

MINERS WILL DONATE FOR FRANKEN-WEENIE--

No waiting. Work on the purist executable at your own pace.  Maybe DJM will flip out some useful code for neoscrypt.  Maybe we will all just get along.       --scryptr

hmm... You must mistake me for Santa Klaus 

Will see what I can do during christmas vacation... 

[AliMan]

MINERS WILL DONATE FOR FRANKEN-WEENIE--

No waiting. Work on the purist executable at your own pace.  Maybe DJM will flip out some useful code for neoscrypt.  Maybe we will all just get along.       --scryptr

hmm... You must mistake me for Santa Klaus 

Will see what I can do during christmas vacation... 

Yo, what's your fastest kernel speed for 980 on neoscrypt?

[Grout]

0.01 BTC guys. This is all I am asking

There you go
697ff02bb2d2e1589eb2b8c40cbfd5584f477cbfe4ff6a942076ee54b8888075

[bobben2]

Since quark was the focus of the most recent changes it proves that cuda 7.5 can perform better than 6.5. I hope these results translate to the other algos.

I have showed that it can be done with quark.
I believe the other algos can be tuned faster as well with more work..

0.01 BTC guys. This is all I am asking

Just sent you
867794d843b271e2647511eff2d959e928bee5642bf9e181b4c9ce66bbf904b7

Keep up the good work!


BTW: My newly acquired ASUS GTX 970 on stock clocks is mining Neoscrypt at ~ 470 kH/s.
cmd line: ccminer -t -a neoscrypt -o <pool>
Version spmod 1.5.63 and CUDA 6.5.19 on Xubuntu 12.04 x64.   Is that what these cards can do or could it
go higher "with the current software"?  

EDIT: Managed to get to ~ 490 kH/s by setting difficulty=256 recognised by the pool..

[djm34]

MINERS WILL DONATE FOR FRANKEN-WEENIE--

No waiting. Work on the purist executable at your own pace.  Maybe DJM will flip out some useful code for neoscrypt.  Maybe we will all just get along.       --scryptr

hmm... You must mistake me for Santa Klaus  

Will see what I can do during christmas vacation...  

Yo, what's your fastest kernel speed for 980 on neoscrypt?

around 850kh/s OC

[sp_]

I submitted another 30KHASH in the x13 algo on the 750ti. Still a few khash to reach the cuda 6.5 speed. (release 72)

[sp_]

Just sent you
867794d843b271e2647511eff2d959e928bee5642bf9e181b4c9ce66bbf904b7
Keep up the good work!

Thanks

[sp_]

0.01 BTC guys. This is all I am asking

There you go
697ff02bb2d2e1589eb2b8c40cbfd5584f477cbfe4ff6a942076ee54b8888075

Thanks

[bensam1231]

Since quark was the focus of the most recent changes it proves that cuda 7.5 can perform better than 6.5. I hope these results translate to the other algos.

I have showed that it can be done with quark.
I believe the other algos can be tuned faster as well with more work..

0.01 BTC guys. This is all I am asking

so you need donation because you believe it can be done ?

Also called crowdfunding.

[sp_]

X11 and neoscrypt is performing terrible in release 74 compiled for cuda 7.5.
I have almost reached the performance of the cuda 6.5 build now with only 4 kernals modified. (x11, x13 (750ti))

release 76-git is 20% faster than a vanilla build of release 74 using cuda 7.5 build (x86)

[chrysophylax]

X11 and neoscrypt is performing terrible in release 74 compiled for cuda 7.5.
I have almost reached the performance of the cuda 6.5 build now with only 4 kernals modified. (x11, x13 (750ti))

release 76-git is 20% faster than a vanilla build of release 74 using cuda 7.5 build (x86)

sp ...

how do you find the test machine going? ...

i think its is powering along - even at the minimal rate that the 750ti runs at ...

in all honesty - i knew this would be a good thing when the code was tuned for c7.5 and wrote that earlier ...

the tests have proven that is the case - and not only the case - but shows there is still room for improvement ...

i am currently building a machine that will mine on all 5 cards for the donation-sp link - and will take the test machine off ... ill set it to x11 and see how that factors in for the speed and longer term performance of the cards with the latest git build ... if the average rate is more than 2800kh in x11 on these cards - then you have succeeded in doing better than c6.5 builds ...

this machine will be ready soon ... in fact - within the next half hour ...

its then sleep for me - then all day work on the other system i have been wanting to build for so long ... some of the components are already here ... the next few weeks will be the rest of the components for the granite 'grunt' system ... ill be building that system in fedora 23 x64 c7.5 ... cant wait ...

keep an eye on the x11 eu stratum at nicehash in the next 30mins ... https://www.nicehash.com/?p=miners&addr=1CTiNJyoUmbdMRACtteRWXhGqtSETYd6Vd&a=3&l=0 ... ill leave that running for a couple of days to donate a further bit of btc for you ...

#crysx

[theotherme]

Since quark was the focus of the most recent changes it proves that cuda 7.5 can perform better than 6.5. I hope these results translate to the other algos.

I have showed that it can be done with quark.
I believe the other algos can be tuned faster as well with more work..

0.01 BTC guys. This is all I am asking

so you need donation because you believe it can be done ?

Also called crowdfunding.

except we know that nothing noticeable comes out at the end...
so as far as I am concerned, these are just baseless promises...

[sp_]

except we know that nothing noticeable comes out at the end...
so as far as I am concerned, these are just baseless promises...

I just gave you 5% more quark on compute 5.2 devices(release 76). Everybody Know I have a faster private kernal.

But for only a few beers in donations,  I will not publish it.


For the donators: if you donate a total amount of 0.1 btc you can get a copy of my private kernals.

1. Spreadcoin 10-20% faster (0.1BTC) (full sourcecode and linux compatible)
2. Cryptonight 10% faster (0.1BTC)
3. pentablake 100-120% faster (0.3BTC)

Please restore the performance of your neoscrypt kernal on cuda 7.5. My 750ti is only hashing @ 60KHASH.  66% slower

[theotherme]

except we know that nothing noticeable comes out at the end...
so as far as I am concerned, these are just baseless promises...

I just gave you 5% more quark on compute 5.2 devices(release 76). Everybody Know I have a faster private kernal.

oh yes, I forgot the 5% stuff, we see all the time and nobody can notice 

[sp_]

X11 and neoscrypt is performing terrible in release 74 compiled for cuda 7.5.
I have almost reached the performance of the cuda 6.5 build now with only 4 kernals modified. (x11, x13 (750ti))
release 76-git is 20% faster than a vanilla build of release 74 using cuda 7.5 build (x86)

sp ...
how do you find the test machine going? ...
i think its is powering along - even at the minimal rate that the 750ti runs at ...
in all honesty - i knew this would be a good thing when the code was tuned for c7.5 and wrote that earlier ...
the tests have proven that is the case - and not only the case - but shows there is still room for improvement ...
i am currently building a machine that will mine on all 5 cards for the donation-sp link - and will take the test machine off ... ill set it to x11 and see how that factors in for the speed and longer term performance of the cards with the latest git build ... if the average rate is more than 2800kh in x11 on these cards - then you have succeeded in doing better than c6.5 builds ...
this machine will be ready soon ... in fact - within the next half hour ...
its then sleep for me - then all day work on the other system i have been wanting to build for so long ... some of the components are already here ... the next few weeks will be the rest of the components for the granite 'grunt' system ... ill be building that system in fedora 23 x64 c7.5 ... cant wait ...
keep an eye on the x11 eu stratum at nicehash in the next 30mins ... https://www.nicehash.com/?p=miners&addr=1CTiNJyoUmbdMRACtteRWXhGqtSETYd6Vd&a=3&l=0 ... ill leave that running for a couple of days to donate a further bit of btc for you ...
#crysx

Thanks for your support

[sp_]

except we know that nothing noticeable comes out at the end...
so as far as I am concerned, these are just baseless promises...

I just gave you 5% more quark on compute 5.2 devices(release 76). Everybody Know I have a faster private kernal.

oh yes, I forgot the 5% stuff, we see all the time and nobody can notice  

19-september 2014 (ccminer DJM34 version)
http://cryptomining-blog.com/3503-crypto-mining-performance-of-the-new-nvidia-geforce-gtx-980/




Quark was hashing at 12322 on the reference gtx 980 card (2048 shaders)
Quark is now  hashing at 12300 on a overclocked gtx 960 oc. (1024 shaders) and around 20MHASH on the reference 980 cards.(ccminer sp-mod release 76)'

A total of 63% gain