CCminer(SP-MOD) Modded GPU kernels.

[s7icky]

Not trying to talk smack sp_ but i run 4 x 980ti... and really have never seen any BIG improvements in hashrates. Dont get me wrong i love ur work. but constantly asking for moonies and saying something is a whatever increase and no one really ever seeing it? Kinda bullshit if you ask me.

How much is a BIG improvement?

Ummm atleast what he says?

[antantti]

Not trying to talk smack sp_ but i run 4 x 980ti... and really have never seen any BIG improvements in hashrates. Dont get me wrong i love ur work. but constantly asking for moonies and saying something is a whatever increase and no one really ever seeing it? Kinda bullshit if you ask me.

How much is a BIG improvement?

Ummm atleast what he says?

5% ?

[joblo]

Unless someone is holding back the mature algos are probably optimal by now. Most of the improvements now
are device specific tweaks. We'll probably have to wait for pascal and sm5.3 (and cuda 8?) for any major improvement
opportunities in software. Hopefully profits will be higher by then.

[Schleicher]

Also should update the code with the cuda version number so it says cuda 7.5 when launched not important though lol

That is just a hardcoded string and does not reflect how ccminer was actually compiled. A more appropriate comment
would be "optimized for cuda 7.5" unless a system variable is available to read the actual compile environment.

Just replace this code in ccminer.cpp:

Code:

#ifdef WIN32
	printf("\tBuilt with VC++ 2013 and nVidia CUDA SDK 6.5\n\n");
#else
	printf("\tBuilt with the nVidia CUDA SDK 6.5\n\n");
#endif

with this:

Code:

#ifdef _MSC_VER
	printf("Compiled with Visual C++ %d ", _MSC_VER / 100);
#else
#ifdef __clang__
	printf("Compiled with Clang %s ", __clang_version__);
#else
#ifdef __GNUC__
	printf("Compiled with GCC %d.%d ", __GNUC__, __GNUC_MINOR__);
#else
	printf("Compiled with an unknown compiler ");
#endif
#endif
#endif
	printf("using Nvidia CUDA Toolkit %d.%d\n\n", CUDART_VERSION / 1000, (CUDART_VERSION % 1000) / 10);

[joblo]

Also should update the code with the cuda version number so it says cuda 7.5 when launched not important though lol

That is just a hardcoded string and does not reflect how ccminer was actually compiled. A more appropriate comment
would be "optimized for cuda 7.5" unless a system variable is available to read the actual compile environment.

Just replace this code in ccminer.cpp:

Code:

#ifdef WIN32
	printf("\tBuilt with VC++ 2013 and nVidia CUDA SDK 6.5\n\n");
#else
	printf("\tBuilt with the nVidia CUDA SDK 6.5\n\n");
#endif

with this:

Code:

#ifdef _MSC_VER
	printf("Compiled with Visual C++ %d ", _MSC_VER / 100);
#else
#ifdef __clang__
	printf("Compiled with Clang %s ", __clang_version__);
#else
#ifdef __GNUC__
	printf("Compiled with GCC %d.%d ", __GNUC__, __GNUC_MINOR__);
#else
	printf("Compiled with an unknown compiler ");
#endif
#endif
#endif
	printf("using Nvidia CUDA Toolkit %d.%d\n\n", CUDART_VERSION / 1000, (CUDART_VERSION % 1000) / 10);

I knew there had to be one, I just couldn't find it.

[Al_may]

OK, I must have forgotten how to do this but

 how would I start, in windows 7, a CMD or used in a CMD scrypt with an affinity of 4.

just trying to keep the work load off the first 2 for the OS
I have looked it up in google but most had their heads in a dark place

[Al_may]

oh my,
I just updated from .74 on a windows 7 pro and I get this
ccminer.exe is not a valid win 32 application

[joblo]

OK, I must have forgotten how to do this but

 how would I start, in windows 7, a CMD or used in a CMD scrypt with an affinity of 4.

just trying to keep the work load off the first 2 for the OS
I have looked it up in google but most had their heads in a dark place

I'm not sure why you're asking but the --cpu-affinity can be set in ccminer. If you want to do it
in Windows it's something like: start <program> /affinity <n>

I don't think you have anything to worry about with the cpu load of ccminer, but a cpu miner...

[Lenore]

oh my,
I just updated from .74 on a windows 7 pro and I get this
ccminer.exe is not a valid win 32 application

Have you tried combatability mode.  You can pick what OP version u want it to try to run in.

You on a 32 or 64 bit system or do you have a 32 bit os with a 64 bit system?

[Al_may]

oh my,
I just updated from .74 on a windows 7 pro and I get this
ccminer.exe is not a valid win 32 application

well i had to update my 7-zip. all is fine now

[Al_may]

yep 76 is a 50% slow down for neo scrypt  from 586 to 234
 and quark is up 1.04 % from 17206 to 17972
time to run two folders

[joblo]

yep 76 is a 50% slow down for neo scrypt  from 586 to 234
 and quark is up 1.04 % from 17206 to 17972
time to run two folders

Has anyone compiled r76 for sm5.2 using cuda 6.5 (windows or linux to do a direct comparison with cuda 7.5?
I could only do it with 750ti's on Linux and there was virtually no difference.

Edit: however, they were both slower than 1.5.74-cuda6.5.

The numbers (gpu0/gpu1) both EVGA 750ti SC no OC.

            1.5.74(6.5)    1.5.76(6.5)     1.5.76(7.5)
x11         3090/3145      2985/3050       2980/3045
quark       6360/6450      6335/6380       6340/6400
lyra2v2     4715/4755      4680/4715       4680/4715

What a pain getting this to display correctly, this ain't WYSIWYG.

[sp_]

oh my,
I just updated from .74 on a windows 7 pro and I get this
ccminer.exe is not a valid win 32 application

Release 76 will not work with old drivers. you need to upgrade to the latest.

[sp_]

yep 76 is a 50% slow down for neo scrypt  from 586 to 234
 and quark is up 1.04 % from 17206 to 17972
time to run two folders

Your math is wrong.

from 17206 to 17972 is a 4,4519353713821% increase of the hashrate.

[chrysophylax]

tanx for the update sp ... cant wait to compile and see ...

I just released 76 with increased hashrate all over the place. But some of the algos are still slower than release 74. Quark has the most boost this time, and mostly on compute 5.2 devices.

ok great ...
then thats the first thing i will test when i get into the office tomorrow ...
a miner will hash quark on your donation address ( donate-sp.granitecoin.com ) and see how it tests ...
look out for the test on nicehash ( eu stratum ) ...
tanx again mate ... i hope it compiles and works well on the new system ...
#crysx

Just tested quark release 76 on my 980ti g1 gigabyte windforce oc.
27.3 (+1,4MHASH) on the standard clocks(New WORLD RECORD)!
Release 74 is only doing 25.9MHASH.

On the EVGA SSC gtx 960. 11 MHASH on standard clocks. up 0.5 MHASH from release 74

is that stock clocks sp? ...

#crysx

[sp_]

Has anyone compiled r76 for sm5.2 using cuda 6.5 (windows or linux to do a direct comparison with cuda 7.5?
I could only do it with 750ti's on Linux and there was virtually no difference.
Edit: however, they were both slower than 1.5.74-cuda6.5.

This fork is now a cuda 7.5 fork. Upgrade to the latest drivers and compile with cuda 7.5 to get a boost in quark. (compute 5.2 devices) gtx 950, gtx 960, gtx 970, gtx 980, gtx 980ti...

[sp_]

is that stock clocks sp? ...
#crysx

Yes.

[sp_]

How much is a BIG improvement?

Ummm atleast what he says?

5% ?

Here is the checklist to reach the optimal speed:

1. Latest drivers
2. Windows x86
3. Compile for cuda 7.5 (or use my binary)

I get a 5% boost on my testrigs on compute 5.2 devices in the quark algo.

If you do this:

1. Linux
2. 64bit build
3. cuda 6.5

You get a 0% boost in the quark algo.

[chrysophylax]

yep 76 is a 50% slow down for neo scrypt  from 586 to 234
 and quark is up 1.04 % from 17206 to 17972
time to run two folders

Has anyone compiled r76 for sm5.2 using cuda 6.5 (windows or linux to do a direct comparison with cuda 7.5?
I could only do it with 750ti's on Linux and there was virtually no difference.

Edit: however, they were both slower than 1.5.74-cuda6.5.

The numbers (gpu0/gpu1) both EVGA 750ti SC no OC.

            1.5.74(6.5)    1.5.76(6.5)     1.5.76(7.5)
x11         3090/3145      2985/3050       2980/3045
quark       6360/6450      6335/6380       6340/6400
lyra2v2     4715/4755      4680/4715       4680/4715

What a pain getting this to display correctly, this ain't WYSIWYG.

im compiling the the latest as we speak ... i was well enough to drive - so im here in the office at the moment ...

the only thing i can give a comparison rate to is quark ( from 74 - 76 ) on c7.5 ...

that doesnt exactly hep what you are asking - but it may be of interest to you regarding the last compiles i had with fedora ...

btw - i have upgraded to fedora23x64 on the test machine - and compiling with c7.5 and ccminer-spmod76 ...

it is this test machine i will be placing to mine for sp as a donation ... so if all is well - it should be a nice gain - unless fedora / cuda is broken in this version ... if not - im looking forward to some gains ... and sp - expect some hashrate on the donation link for you ...

#crysx

[chrysophylax]

How much is a BIG improvement?

Ummm atleast what he says?

5% ?

Here is the checklist to reach the optimal speed:

1. Latest drivers
2. Windows x86
3. Compile for cuda 7.5 (or use my binary)

I get a 5% boost on my testrigs on compute 5.2 devices in the quark algo.

If you do this:

1. Linux
2. 64bit build
3. cuda 6.5

You get a 0% boost in the quark algo.

though linux build will show in a few minutes as to what it does compiled in f23x64c75 ( ie - fedora 23 x64 cuda 7.5 - im shorthanding from now on ) ...

at least on my end anyway ... as you know - my systems seem to go the complete opposite of what most people were getting ...

look out for the hashrate to show on you link ... https://www.nicehash.com/?p=miners&addr=1CTiNJyoUmbdMRACtteRWXhGqtSETYd6Vd&a=12&l=0 ...

ill do the test on quark as that is a good comparison from the previous v74 ( that was compiled in f22x64c75 ) ...

#crysx