CCminer(SP-MOD) Modded GPU kernels.

[sp_]

I added 0.5MHASH to the qubit algo and 20MHASH in the doom algo(10% faster). on the gtx 970 @github

I compared the latest qubit(release 77+++) with the release 74.

It's faster on the 750ti. (+50Khash)
slower on gtx 960 and gtx 970. (-200khash)

[pallas]

I linked with 6.5, it was the git HEAD of yesterday.

[sp_]

-faster qubit (+5%)
-faster blake/blakecoin (+6.5% since release 74)
-faster doom(luffa 512) (+10%) (compute 5.2)
-faster x11
-faster lyra2v2

1.5.78(sp-MOD) is available here: (02-jan-2015)

https://github.com/sp-hash/ccminer/releases/

The sourcecode is available here:

https://github.com/sp-hash/ccminer

(Cuda 7.5 only. No merged kernals)

Please donate to get more hashrate.

[sp_]

I linked with 6.5, it was the git HEAD of yesterday.

I am tweaking to run faster with the cuda 7.5 compiler. Cuda 6.5 is untested since release 74.

[tbearhere]

@sp  It would be nice if somehow in your ccminer ..you could get the 980ti  to stay at the p0 state..it hashs at the p2 state...which is about 20% less hashs.....my guess. So the hashrates we see on the 980ti is at only 80% efficiency.

[pallas]

@sp  It would be nice if somehow in your ccminer ..you could get the 980ti  to stay at the p0 state..it hashs at the p2 state...which is about 20% less hashs.....my guess. So the hashrates we see on the 980ti is at only 80% efficiency.

My 970s have always hashed at p2. Maybe cause of the Linux drivers.

[ZeroFossilFuel]

I'm having trouble compiling with CUDA 7.5.  I installed 7.5.18 from the nVidia web site but when I run ccminer it still says compiled with CUDA 6.5?  I'm stumped. 

[antantti]

@sp  It would be nice if somehow in your ccminer ..you could get the 980ti  to stay at the p0 state..it hashs at the p2 state...which is about 20% less hashs.....my guess. So the hashrates we see on the 980ti is at only 80% efficiency.

My 970s have always hashed at p2. Maybe cause of the Linux drivers.

Powerstate only affects memory hard algos on my 970 windows rig, at p2 state it is impossible to overclock memory. Nvidia Inspector works for me, just choose overclocking - P2 - slider to the right - save.

Resets at reboot.

[sp_]

I'm having trouble compiling with CUDA 7.5.  I installed 7.5.18 from the nVidia web site but when I run ccminer it still says compiled with CUDA 6.5?  I'm stumped. 

Do you have the latest version of the sourcecode?

release 78 has this in the heading:

Compiled with Visual C++ 18 using Nvidia CUDA Toolkit 7.5

[tbearhere]

@sp  It would be nice if somehow in your ccminer ..you could get the 980ti  to stay at the p0 state..it hashs at the p2 state...which is about 20% less hashs.....my guess. So the hashrates we see on the 980ti is at only 80% efficiency.

My 970s have always hashed at p2. Maybe cause of the Linux drivers.

Powerstate only affects memory hard algos on my 970 windows rig, at p2 state it is impossible to overclock memory. Nvidia Inspector works for me, just choose overclocking - P2 - slider to the right - save.

Resets at reboot.

Thx  I'll try it.......but 980ti at the p2 state clocks are at 1/2  so imagine if we got them to p0  100% and then overclocked. Its got to add some hashrate...a lot

[antantti]

@sp  It would be nice if somehow in your ccminer ..you could get the 980ti  to stay at the p0 state..it hashs at the p2 state...which is about 20% less hashs.....my guess. So the hashrates we see on the 980ti is at only 80% efficiency.

My 970s have always hashed at p2. Maybe cause of the Linux drivers.

Powerstate only affects memory hard algos on my 970 windows rig, at p2 state it is impossible to overclock memory. Nvidia Inspector works for me, just choose overclocking - P2 - slider to the right - save.

Resets at reboot.

Thx  I'll try it.......but 980ti at the p2 state clocks are at 1/2  so imagine if we got them to p0  100% and then overclocked. Its got to add some hashrate...a lot

Are you sure about that? Under ccminer load your core clocks should be somewhere around 1400-1500MHz area.

[sp_]

I am failing to  p0 state on my gtx 960 and gtx 970.

nvidiaInspector.exe -setPstateLimit:0,0
nvidiaInspector.exe -setPstateLimit:1,0
nvidiaInspector.exe -setPstateLimit:2,0
nvidiaInspector.exe -setPstateLimit:3,0

nvidiaInspector.exe -forcepstate:0,3
nvidiaInspector.exe -forcepstate:1,3
nvidiaInspector.exe -forcepstate:2,3
nvidiaInspector.exe -forcepstate:3,3


how can I do it with nvidia inspector?

[dominuspro]

No gains with p0 state on 960, 970 and 980. Only ETH gains some % with memory oc.
Anyway I managed to put all the cards to p0 state also in windows. It is the same "trick" as in linux using nvidia-smi tool.

I'm not responsible if You kill Your GPU. The risk is Yours.
The procedure is:
1) open cmd.exe with the admin privileges
2) cd C:\Program Files\NVIDIA Corporation\NVSMI
3) nvidia-smi -q -d SUPPORTED_CLOCKS -i 0
4) nvidia-smi -ac 3505,1455 -i 0

-i 0 means display adapter 0. -i 4 would mean display adapter 4.
Step 3 is used to show the possible clock settings combination for each power state. The numbers will change if You overclock Your gpu before running step 3.
The result after typing step 3 would be looking like that:

Code:

C:\Windows\system32>cd C:\Program Files\NVIDIA Corporation\NVSMI

C:\Program Files\NVIDIA Corporation\NVSMI>nvidia-smi -q -d SUPPORTED_CLOCKS -i 0


==============NVSMI LOG==============

Timestamp                           : Sat Jan 02 19:09:48 2016
Driver Version                      : 359.06

Attached GPUs                       : 5
GPU 0000:01:00.0
    Supported Clocks
        Memory                      : 3505 MHz
            Graphics                : 1635 MHz
            Graphics                : 1623 MHz
            Graphics                : 1610 MHz
            Graphics                : 1598 MHz
            Graphics                : 1585 MHz
            Graphics                : 1572 MHz
            Graphics                : 1560 MHz
            Graphics                : 1547 MHz
            Graphics                : 1534 MHz
            Graphics                : 1522 MHz
            Graphics                : 1509 MHz
            Graphics                : 1496 MHz
            Graphics                : 1484 MHz
            Graphics                : 1471 MHz
            Graphics                : 1458 MHz
            Graphics                : 1446 MHz
            Graphics                : 1433 MHz
            Graphics                : 1420 MHz
            Graphics                : 1408 MHz
            Graphics                : 1395 MHz

It always starts with the clocks of the p0 state. In my example it shows memory 3505 after that You can find listed all the possible graphics settings. You must chose one and type it exactly the same number in the step 4.

Example:
nvidia-smi -ac 3505,1446 -i 0
The nvidia inspector shows Your card in p0 and You can overclock also the memory with msi afterburner or any other oc tool.

If You type nvidia-smi -ac 3505,1440 -i 0 it won't be accepted because 1440 is not in a list of matching Mhz for memory clock 3505.

I'm not responsible if You kill Your GPU. The risk is Yours.

[myagui]

I am failing to  p0 state on my gtx 960 and gtx 970.
how can I do it with nvidia inspector?

You don't. With nvidia inspector your 9xx cards will always be stuck with P2 (which is just shy of the top memory bins). There's other ways to get there as someone else posted though.

[antantti]

I am failing to  p0 state on my gtx 960 and gtx 970.
how can I do it with nvidia inspector?

You don't. With nvidia inspector your 9xx cards will always be stuck with P2 (which is just shy of the top memory bins). There's other ways to get there as someone else posted though.

Yep, you are right, no p0 state with inspector. But you can overclock your memory to p0 levels at p2 if you want.

[ZeroFossilFuel]

I'm having trouble compiling with CUDA 7.5.  I installed 7.5.18 from the nVidia web site but when I run ccminer it still says compiled with CUDA 6.5?  I'm stumped. 

Do you have the latest version of the sourcecode?

release 78 has this in the heading:

Compiled with Visual C++ 18 using Nvidia CUDA Toolkit 7.5

Disregard my last post. Looks like I had a partially corrupt hybrid CUDA 6.5/7.5. I reverted back to nouveau drivers, ununstalled CUDA completely, started again from scratch and voi-la! It compiles using 7.5. Didn't see any hash rate improvements, though.   

[s7icky]

sp_ how much do you want for your quark private miner? or DJM? or even x11 and Lyra2REv2

[djm34]

sp_ how much do you want for your quark private miner? or DJM? or even x11 and Lyra2REv2

I am not for sell 

[sp_]

I'm having trouble compiling with CUDA 7.5.  I installed 7.5.18 from the nVidia web site but when I run ccminer it still says compiled with CUDA 6.5?  I'm stumped. 

Do you have the latest version of the sourcecode?

release 78 has this in the heading:

Compiled with Visual C++ 18 using Nvidia CUDA Toolkit 7.5

Disregard my last post. Looks like I had a partially corrupt hybrid CUDA 6.5/7.5. I reverted back to nouveau drivers, ununstalled CUDA completely, started again from scratch and voi-la! It compiles using 7.5. Didn't see any hash rate improvements, though.   

Some kernals are faster. Some are slower.

[sp_]

sp_ how much do you want for your quark private miner? or DJM? or even x11 and Lyra2REv2

I am not for sell 

ESL