CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 1119.

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: rednoW on April 26, 2015, 01:14:30 PM

gtx750 oc'ed
#47 vs. Commit 742
skein 83210 vs. 83620
quark 5810 vs 5824 (hashrate fluctuating, maybe incorrect measuring)
conclusion: commit 742 is best for me ...

For skein you should use the latest version. Fixed some bugs in the hash. Checking 32 bits was not enough. Increased to 64 bits.

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Release 47:

Gtx980 default clock

Skein: 321Mhash

ryen123

sr. member

Activity: 292

Merit: 250

Tried the scrypt algo. I get the error seen above. And it just sits there does nothing.

rednoW

legendary

Activity: 1510

Merit: 1003

gtx750 oc'ed

#47 vs. Commit 742

skein 83210 vs. 83620
quark 5810 vs 5824 (hashrate fluctuating, maybe incorrect measuring)

conclusion: commit 742 is best for me ...

rednoW

legendary

Activity: 1510

Merit: 1003

Forget about -g ... it just doesn't work or has no advantages

frazier34567

member

Activity: 95

Merit: 10

I am running 6X750ti EVGA SC (no OC) and for quark when I run -i 22 I get 36744. When I add -g 2 or any number of threads my CPU goes to 99% and I actually run slower at about 36100-250. I have tried the release 46 and also compiled my own using commit 757 and both go to 99% cpu.

I am on windows 8.1 Pro with an i3 processor with 8 GB of RAM.

Just tried 47 and without an -i or -g parameter I get ~~36533~~37120

When I try -i 22 or -i 21 it crashes.

I get nonce errors

[2015-04-26 13:04:34] GPU #5: GeForce GTX 750 Ti, 38196 kH/s[0m
[2015-04-26 13:04:34] GPU #4: result for nonce $769C2CC7 does not validate on CPU![0m

Then this

Cuda error in func 'cuda_check_cpu_setTarget' at line 28 : unspecified launch failure.

EDIT: Rebooted and now it works up to -i 23

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

1.5.47(sp-mod)
@sp-hash sp-hash released this 15 minutes ago

-skein 38% faster (192->265MHASH on the gtx 970)
-Faster Keccak (now support higher intensity values)
-small speedup in quark and scypt

1.5.47(sp-MOD) is available here: (26-april-2015)

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

The sourcecode is available here:

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

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: sp_ on April 26, 2015, 08:46:23 AM

Quote from: sp_ on April 26, 2015, 07:00:21 AM

I have added another 9% in skein. Most gain on compute 5.2. Will clean the code abit and submit to github
the 970 is now hashing at 265MHASH.
The total gain from version 46 on the 970 is 38%

I get some lower rates on the pool. Will investigate.

Submitted some fixes, the hashrate looks good now but get some rejects / duplicate shares.

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Quote from: sp_ on April 26, 2015, 07:00:21 AM

I have added another 9% in skein. Most gain on compute 5.2. Will clean the code abit and submit to github
the 970 is now hashing at 265MHASH.
The total gain from version 46 on the 970 is 38%

I get some lower rates on the pool. Will investigate.

chrysophylax

legendary

Activity: 2912

Merit: 1091

--- ChainWorks Industries ---

Quote from: sp_ on April 26, 2015, 08:17:14 AM

Added keccak boost.

Keccak can now be run with intensity 28, before only 21 was possible.

defaults are set to 27 for compute 5.0 and 28 for compute 5,2

most i could run keccak on westhash was -i 24.9 ...

will recompile and see how that goes soon ...

tanx sp ...

#crysx

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

Added keccak boost.

Keccak can now be run with intensity 28, before only 21 was possible.

defaults are set to 27 for compute 5.0 and 28 for compute 5,2

sp_

legendary

Activity: 2926

Merit: 1087

Team Black developer

I have added another 9% in skein. Most gain on compute 5.2. Will clean the code abit and submit to github

the 970 is now hashing at 265MHASH.

The total gain from version 46 on the 970 is 38%

chrysophylax

legendary

Activity: 2912

Merit: 1091

--- ChainWorks Industries ---

Quote from: scryptr on April 25, 2015, 10:26:20 PM

Quote from: chrysophylax on April 25, 2015, 08:51:02 PM

Quote from: hashbrown9000 on April 25, 2015, 06:38:41 PM

To the linux guys: what version of CUDA are you compiling with?

6.0 ...

we have been playing with 6.5 and it seems to work quite well ...

our miners are now all running 6.5 compiled ccminer and they seem to be stable ...

but the moment a major crash happens - we revert back to the 6.0 compiled miners and they just work ...

#crysx

CUDA 6.5 --

The stuff from SP_ compiles on CUDA 6.5. I believe that tpruvot moved to CUDA 7.0, but he takes pains to keep his miners compatible with older nVidia cards. I don't personally know if CUDA 7.0 can compile programs built for 6.5 properly, although I am curious. I would install CUDA Toolkit 7.0 on my system if it would work well with the code SP_ produces. CBuchner's CudaMiner was written for CUDA 5.5, tpruvot has a version re-written for 6.5.

I'm looking forward to moving to CUDA 7.0, especially if it produces more hash. --scryptr

same here - though cuda 7.0 is not compiling anywhere near as compliant as 6.5 is ... for now anyway @scryptr ...

should be interesting to see how this all works a few months down the track when nvidia change the whole playing field with a new chipset once again ...

#crysx

rednoW

legendary

Activity: 1510

Merit: 1003

Quote from: tbearhere on April 25, 2015, 05:22:30 PM

#46
QUARK HASH 750ti FTW - 6.35-6.6Mh/s Showing on command window..about 1mh/s more for my rig...but at pool 1mh/s less..staying with #43 the best so far. And the 3 750ti on this computer with #46 drags down the computer.

I just compared again #43 and #46 with equal -i parameters. -i 19.8 was the best for #43 and with such intensity #43 is faster then #46 with -i 19.8.

But default intensity for #46 is -i 22. #43 just didn't work with -i 22.
And with -i 22 (or without -i) #46 is faster then #43 with -i 19.8 (or without i).
My conclusion is that #43 is more efficient per thread but as it cannot pass -i 20 border it is slower.
If you will count hashes per watt then it maybe becomes that #43 is more efficient as in my case #43 never takes more 58% TDP but #46 takes up to 65% TDP

rednoW

legendary

Activity: 1510

Merit: 1003

Quote from: scryptr on April 25, 2015, 10:26:20 PM

I'm looking forward to moving to CUDA 7.0, especially if it produces more hash. --scryptr

sp_ ccminer compiled with CUDA 7.0 produces incorrect hash ... i tried it some time ago on windows

scryptr

legendary

Activity: 1797

Merit: 1028

Quote from: chrysophylax on April 25, 2015, 08:51:02 PM

Quote from: hashbrown9000 on April 25, 2015, 06:38:41 PM

To the linux guys: what version of CUDA are you compiling with?

6.0 ...

we have been playing with 6.5 and it seems to work quite well ...

our miners are now all running 6.5 compiled ccminer and they seem to be stable ...

but the moment a major crash happens - we revert back to the 6.0 compiled miners and they just work ...

#crysx

CUDA 6.5 --

The stuff from SP_ compiles on CUDA 6.5. I believe that tpruvot moved to CUDA 7.0, but he takes pains to keep his miners compatible with older nVidia cards. I don't personally know if CUDA 7.0 can compile programs built for 6.5 properly, although I am curious. I would install CUDA Toolkit 7.0 on my system if it would work well with the code SP_ produces. CBuchner's CudaMiner was written for CUDA 5.5, tpruvot has a version re-written for 6.5.

I'm looking forward to moving to CUDA 7.0, especially if it produces more hash. --scryptr

chrysophylax

legendary

Activity: 2912

Merit: 1091

--- ChainWorks Industries ---

Quote from: hashbrown9000 on April 25, 2015, 06:38:41 PM

To the linux guys: what version of CUDA are you compiling with?

6.0 ...

we have been playing with 6.5 and it seems to work quite well ...

our miners are now all running 6.5 compiled ccminer and they seem to be stable ...

but the moment a major crash happens - we revert back to the 6.0 compiled miners and they just work ...

#crysx

DougB62

hero member

Activity: 672

Merit: 500

Banned: For Your Protection

Quote from: sp_ on April 25, 2015, 04:57:43 PM

The problem with NVIDIA cards is that they have a dynamic clockrate. If you push the card too much, it will downclock automaticly. Base clock vs boost clock. In the latest mods I have tried to reduce the number of gpu-threads to increase the boost, and reduce the power consumption.

nvidiaInspector.exe -forcepstate ??

tbearhere

legendary

Activity: 3164

Merit: 1003

Quote from: hashbrown9000 on April 25, 2015, 06:38:00 PM

Code:

hashbrown9000 You mean that if it crashes it with auto restart the miner right away?
thx
ps Please look at my post right above this.

No, this just restarts the nvidia driver without restarting the computer. My main display runs on an old AMD 6850, and the other GPU in the system is the 750ti.

I never tried restarting the driver using precisionX.

Ok thx

hashbrown9000

sr. member

Activity: 427

Merit: 250

To the linux guys: what version of CUDA are you compiling with?

Topic: CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 1119. (Read 2347601 times)