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

Klaus_t implementation was pretty good, but the launchconfiguration of the kernal was way off. I submitted a 17.5% speed increase to github. (750ti)

Interesting to see bitcoin (sha256) support added.  No chance of profit but fun to have most of the algos supported in one miner.  Of note, this doesn't seem to be a very optimal implementation.  With cgminer (opencl) I was getting about 405,000 kh/s on my 2 x 750 Ti setup.  With release 34 ccminer I'm down to about 345,000 kh/s.  Still, it sits at the very bottom of the profitability list with either hash rate so I'm not too concerned.  It burns many more times in power than it earns.

Interesting to see bitcoin (sha256) support added.  No chance of profit but fun to have most of the algos supported in one miner.  Of note, this doesn't seem to be a very optimal implementation.  With cgminer (opencl) I was getting about 405,000 kh/s on my 2 x 750 Ti setup.  With release 34 ccminer I'm down to about 345,000 kh/s.  Still, it sits at the very bottom of the profitability list with either hash rate so I'm not too concerned.  It burns many more times in power than it earns.

Nobody mining x11 anymore? what rates are you getting? (ppol vs miner) (970 and 980 is untested so please test)

Use a low difficulty

on nicehash.com you can add the difficulty in the password like this: -p=d=0.02

The code was added by klaus-t. Probobly a pure C port without any cuda.
The code could be optimized, but it doesn't matter.  Even if I manage to push the speed to 1GHASH---> not profitable.

But perhaps I will try anyway...

I will add some more speedup in x13,x14,x15 today.  Similar to the fresh/x11 optimalizations. Divide the stream into two streams and run in paralell.

Nobody mining x11 anymore? what rates are you getting? (ppol vs miner) (970 and 980 is untested so please test)

Use a low difficulty

on nicehash.com you can add the difficulty in the password like this: -p=d=0.02

try d=0.01 or d=0.005. Or empty diff parameter.
I get a higher hashrate. but my rig has more than one card.

that is your pool is it not ocminer? ...

#crysx

yes, it works. Good in "fresh".
Strange but for "quark" on compute 3.0 original ccminer 1.2 is the best, just for fun

~2830 khash/s same on release 31 and 34 (as miner shows). Have no long run to test pool shown rate
d = 0.02

What rates are you getting in x11?

quark: ~5550kh (on release 31 is ~5600kh) up to 61% of modded TDP 65w (cool)

yes, it works. Good in "fresh".
Strange but for "quark" on compute 3.0 original ccminer 1.2 is the best, just for fun
Tried to build your release 34 in x64 mode. Small performance drop in all algos.
Test comp: Athlon64X2 3ghz, gtx 750 (1470gpu/1550mem), win7x64
rates on your original release34 build are
fresh: ~3450kh  
quark: ~5550kh (on release 31 is ~5600kh) up to 61% of modded TDP 65w (cool)
release 34 seems to work better with yaamp then release 31

just changing settings to compute_30,sm_30 in CUDA C/C++ -> Device -> Code Generation in VS2013 project preferences
leads to results not approved by CPU.
Not that i need it, just tried ))).

As well as trying to compile with CUDA 7.0

Any step from default config leads to not working code ...

3.0   GeForce GTX 770, GeForce GTX 760, GeForce GT 740, GeForce GTX 690, GeForce GTX 680, GeForce GTX 670, GeForce GTX 660 Ti, GeForce GTX 660, GeForce GTX 650 Ti BOOST, GeForce GTX 650 Ti, GeForce GTX 650, GeForce GTX 780M, GeForce GTX 770M, GeForce GTX 765M, GeForce GTX 760M, GeForce GTX 680MX, GeForce GTX 680M, GeForce GTX 675MX, GeForce GTX 670MX, GeForce GTX 660M, GeForce GT 750M, GeForce GT 650M, GeForce GT 745M, GeForce GT 645M, GeForce GT 740M, GeForce GT 730M, GeForce GT 640M, GeForce GT 640M LE, GeForce GT 735M, GeForce GT 730M, Quadro K5000, Quadro K4200, Quadro K4000, Quadro K2000, Quadro K2000D, Quadro K600, Quadro K420, Quadro K500M, Quadro K510M, Quadro K610M, Quadro K1000M, Quadro K2000M, Quadro K1100M, Quadro K2100M, Quadro K3000M, Quadro K3100M, Quadro K4000M, Quadro K5000M, Quadro K4100M, Quadro K5100M, Tesla K10

3.5   GeForce GTX TITAN Z, GeForce GTX TITAN Black, GeForce GTX TITAN, GeForce GTX 780 Ti, GeForce GTX 780, GeForce GT 640 (GDDR5), GeForce GT 630 v2, Quadro K6000, Quadro K5200, Tesla K40, Tesla K20x, Tesla K20

3.7   Tesla K80

5.0   GeForce GTX 750 Ti, GeForce GTX 750, GeForce GTX 860M, GeForce GTX 850M, GeForce 845M, GeForce 840M, GeForce 830M, Quadro K2200, Quadro K620, Quadro K620M

5.2   GeForce GTX 980, GeForce GTX 970, GeForce GTX 960, GeForce GTX 980M, GeForce GTX 970M, GeForce GTX 965M

yeah. It might work on compute 3.5 though..

Use this version (1.5.2-git)

https://bitcointalksearch.org/topic/ann-ccminer-23-opensource-gpl-tpruvot-770064

it works.

just changing settings to compute_30,sm_30 in CUDA C/C++ -> Device -> Code Generation in VS2013 project preferences
leads to results not approved by CPU.
Not that i need it, just tried ))).
As well as trying to compile with CUDA 7.0
Any step from default config leads to not working code ...

Interesting to see bitcoin (sha256) support added.  No chance of profit but fun to have most of the algos supported in one miner.  Of note, this doesn't seem to be a very optimal implementation.  With cgminer (opencl) I was getting about 405,000 kh/s on my 2 x 750 Ti setup.  With release 34 ccminer I'm down to about 345,000 kh/s.  Still, it sits at the very bottom of the profitability list with either hash rate so I'm not too concerned.  It burns many more times in power than it earns.

K4000 is using Compute 3.0. Should work If you build yourself. My binaries are always build with compute 5.0 and 5.2.