CCminer(SP-MOD) Modded GPU kernels.

[sp_]

submitted a 40khash increase in lyra2 on the 750ti only. (3.5%)

(reduced the register usage from 185 to 113.)

[CapnBDL]

FYI: CUDA 7.5RC just out.

[flipclip]

So now there is yiimp?

http://yiimp.ccminer.org/

[Epsylon3]

yiimp is a "test pool" i try to set up... without auto exchange, i will update the main page to explain better soon...

will not be like the yaamp multipool system which require a lot of attention about trades

else... CUDA 7.5 really improve ccminer, on almost all algos :p

[scryptr]

DJM34 and LYRA2 --

I was able to get DJM34's Windows binary to run on my Win 8 x64 rig.  This rig has 5x750ti SSC and 1x960 4GB FTW.

Overall, the rig is faster by almost 2Mhash.  My 750ti cards run at 1050kh/s each, and the 4GB 960 FTW gets 1175kh/s while mining Lyra2.  This is the first time the 960 has run faster than the 750ti cards.  Formerly, it ran at 500kh/s (+/- 75kh/s), compared to 725kh/s for the 750ti cards.

On my Win 7 x64 box, where my 2gb 960 SSC is the only graphics card, the DJM34 binary won't launch, as I stated on the previous page.

On my Linux boxes, SP_'s build 843 compiled and mines Lyra2 at 1850kh/s on my 970 FTW+ cards, and at 1050kh/s on my 750ti FTW cards.  The 750ti FTW cards were running at 825kh/s on the SP_'s release dot 50.

--scryptr

[CapnBDL]

yiimp is a "test pool" i try to set up... without auto exchange, i will update the main page to explain better soon...

will not be like the yaamp multipool system which require a lot of attention about trades

else... CUDA 7.5 really improve ccminer, on almost all algos :p

I don't know how you can say CUDA7.5 does so much better. It was just put out to developers, hence the 'RC' designation. Stands for 'Release Candidate', meaning it's in the early stages.

Concerning your 'test pool'; I wouldn't broadcast you are trying this until you are ready to pay-up! I almost started mining there thinking I would be paid for the work I was doing. Just sayin'!

[antonio8]

yiimp is a "test pool" i try to set up... without auto exchange, i will update the main page to explain better soon...

will not be like the yaamp multipool system which require a lot of attention about trades

else... CUDA 7.5 really improve ccminer, on almost all algos :p

I don't know how you can say CUDA7.5 does so much better. It was just put out to developers, hence the 'RC' designation. Stands for 'Release Candidate', meaning it's in the early stages.

Concerning your 'test pool'; I wouldn't broadcast you are trying this until you are ready to pay-up! I almost started mining there thinking I would be paid for the work I was doing. Just sayin'!

[scryptr]

DJM34, SP_ --

I flipped you each a nickle.  Thank you for your hard work!  I hope my 960's will be able to mine Lyra2 on Windows at about 1250kh/s soon, maybe more!

Thanks!       --scryptr

P.S.  I was able to get DJM34's Windows binary to run on my Win 7 x64 system with a 2GB GTX960 SSC with ONLY the performance setting of "-i 16.3".  No other performance settings were used.  Algo, username, password were as standard.

Result:  1175kh/s mining Lyra2       --scryptr

[CapnBDL]

Not lookin' to start a war. Made those comments so that maybe noobs wouldn't make mistakes. On a development thread like this...sooo many will be confused. That's all. Comments need to be FULLY explained (ie. if you are part of the CUDA team, let us know, etc), otherwise noobs will think they may be missing an upgrade (& it's not even released yet. Heck, 7 is questionable/buggy.).

And a 'test pool'...really, and you don't mention that to start with? I hope you own lots of DASH, cuz I want my cut!! Kiddin', but could have ended badly.

[sp_]

On my Linux boxes, SP_'s build 843 compiled and mines Lyra2 at 1850kh/s on my 970 FTW+ cards, and at 1050kh/s on my 750ti FTW cards.  The 750ti FTW cards were running at 825kh/s on the SP_'s release dot 50.

Did you try after my latest commit? I get 40khash + on my gigabyte windforce cards with a 6pins connector.(750ti) The compute 5.2 cards are unchanged as they use another kernal.

Here is the commit:

https://github.com/sp-hash/ccminer/commit/384d4cc461d38fdfb2243cb806806cdccad98074

The commit is not big but it reduces the register usage from 185 to 113. and reduces the codesize wich gives less pressure on the instructioncache.
(less memory usage)

[djm34]

Not lookin' to start a war. Made those comments so that maybe noobs wouldn't make mistakes. On a development thread like this...sooo many will be confused. That's all. Comments need to be FULLY explained (ie. if you are part of the CUDA team, let us know, etc), otherwise noobs will think they may be missing an upgrade (& it's not even released yet. Heck, 7 is questionable/buggy.).

And a 'test pool'...really, and you don't mention that to start with? I hope you own lots of DASH, cuz I want my cut!! Kiddin', but could have ended badly.

You are the one sounding a bit like a noob actually... (no one will do his presentation every day, it is up to you to know who is who  )

regarding cuda 7.5, there are a bit of good and a bit of bad...
on lyra2re, there is a clear +100kh/s on the 980 and +60 on the 750ti (from 1140 to 1200kh/s on my card oc at +150/+150) and also a clear -700kh/s on the 780ti and it is worst on the new neoscrypt code (unpublished) even though some aspect are better...

[djm34]

On my Linux boxes, SP_'s build 843 compiled and mines Lyra2 at 1850kh/s on my 970 FTW+ cards, and at 1050kh/s on my 750ti FTW cards.  The 750ti FTW cards were running at 825kh/s on the SP_'s release dot 50.

Did you try after my latest commit? I get 40khash + on my gigabyte windforce cards with a 6pins connector.(750ti) The compute 5.2 cards are unchanged as they use another kernal.

Here is the commit:

https://github.com/sp-hash/ccminer/commit/384d4cc461d38fdfb2243cb806806cdccad98074

The commit is not big but it reduces the register usage from 185 to 113. and reduces the codesize wich gives less pressure on the instructioncache.
(less memory usage)

the pragma unroll were chosen with care and they enhance the hashrate by about that same amount on one of my card (most likely the 980, that might decrease the hashrate on the 900 serie...)

[djm34]

DJM34, SP_ --

I flipped you each a nickle.  Thank you for your hard work!  I hope my 960's will be able to mine Lyra2 on Windows at about 1250kh/s soon, maybe more!

Thanks!       --scryptr

P.S.  I was able to get DJM34's Windows binary to run on my Win 7 x64 system with a 2GB GTX960 SSC with ONLY the performance setting of "-i 16.3".  No other performance settings were used.  Algo, username, password were as standard.

Result:  1175kh/s mining Lyra2       --scryptr

thanks,
don't forget to run at p0 state using nvidia-smi , that gives the possibility to oc the memclock (it will run also at a somewhat)

[bensam1231]

DJM34, SP_ --

I flipped you each a nickle.  Thank you for your hard work!  I hope my 960's will be able to mine Lyra2 on Windows at about 1250kh/s soon, maybe more!

Thanks!       --scryptr

P.S.  I was able to get DJM34's Windows binary to run on my Win 7 x64 system with a 2GB GTX960 SSC with ONLY the performance setting of "-i 16.3".  No other performance settings were used.  Algo, username, password were as standard.

Result:  1175kh/s mining Lyra2       --scryptr

thanks,
don't forget to run at p0 state using nvidia-smi , that gives the possibility to oc the memclock (it will run also at a somewhat)

From what I've seen memory OCs aren't worth it. They give you a tiny bit of extra hash and they wreck your efficiency. Like 5% more hashrate for 15% more power.

[djm34]

DJM34, SP_ --

I flipped you each a nickle.  Thank you for your hard work!  I hope my 960's will be able to mine Lyra2 on Windows at about 1250kh/s soon, maybe more!

Thanks!       --scryptr

P.S.  I was able to get DJM34's Windows binary to run on my Win 7 x64 system with a 2GB GTX960 SSC with ONLY the performance setting of "-i 16.3".  No other performance settings were used.  Algo, username, password were as standard.

Result:  1175kh/s mining Lyra2       --scryptr

thanks,
don't forget to run at p0 state using nvidia-smi , that gives the possibility to oc the memclock (it will run also at a somewhat)

From what I've seen memory OCs aren't worth it. They give you a tiny bit of extra hash and they wreck your efficiency. Like 5% more hashrate for 15% more power.

well they are for memory hard algo as it decreases the frame buffer usage... (meaning less bottleneck at that level)
and if you have a large number of cards, you probably want a moderate power usage, if you are limited in gpu ressource you want to get the highest hashrate

[sp_]

the pragma unroll were chosen with care and they enhance the hashrate by about that same amount on one of my card (most likely the 980, that might decrease the hashrate on the 900 serie...)

Yes, and they work good on the highendcards, but not so good on the 750ti. (compute5.0) You have 2 kernals, one for the compute 50 and one for the others. I halved the threads per block and removed some of the pragma unrolls in the 5.0 kernal. 3.5-4% gain.

[scryptr]

On my Linux boxes, SP_'s build 843 compiled and mines Lyra2 at 1850kh/s on my 970 FTW+ cards, and at 1050kh/s on my 750ti FTW cards.  The 750ti FTW cards were running at 825kh/s on the SP_'s release dot 50.

Did you try after my latest commit? I get 40khash + on my gigabyte windforce cards with a 6pins connector.(750ti) The compute 5.2 cards are unchanged as they use another kernal.

Here is the commit:

https://github.com/sp-hash/ccminer/commit/384d4cc461d38fdfb2243cb806806cdccad98074

The commit is not big but it reduces the register usage from 185 to 113. and reduces the codesize wich gives less pressure on the instructioncache.
(less memory usage)

COMMIT/BUILD #843--

Each commit to GitHub increments the commit number (Upper Left Hand corner)  There is also a commit hash number, but it is not sequential, so I don't use it.  I just checked and your GitHub commit number is 843.  That is the commit that I built and am currently mining with; it is maybe 12 hours old now.       --scryptr

[scryptr]

DJM34, SP_ --

I flipped you each a nickle.  Thank you for your hard work!  I hope my 960's will be able to mine Lyra2 on Windows at about 1250kh/s soon, maybe more!

Thanks!       --scryptr

P.S.  I was able to get DJM34's Windows binary to run on my Win 7 x64 system with a 2GB GTX960 SSC with ONLY the performance setting of "-i 16.3".  No other performance settings were used.  Algo, username, password were as standard.

Result:  1175kh/s mining Lyra2       --scryptr

thanks,
don't forget to run at p0 state using nvidia-smi , that gives the possibility to oc the memclock (it will run also at a somewhat)

From what I've seen memory OCs aren't worth it. They give you a tiny bit of extra hash and they wreck your efficiency. Like 5% more hashrate for 15% more power.

well they are for memory hard algo as it decreases the frame buffer usage... (meaning less bottleneck at that level)
and if you have a large number of cards, you probably want a moderate power usage, if you are limited in gpu ressource you want to get the highest hashrate

OVERCLOCKING--

I am running DJM34's Windows binary with an intensity setting of "-i 16.3"' and +100 core / +300 mem overclock utilizing EVGA PrecisionX 16.  The result is 1200kh/s on my single 2GB GTX 960 SSC.  I earlier reported 1175kh/s with a lower overclock of +80/+240.  The overclock of +100/+300 was the highest stable overclock when mining Quark, but recent Quark code changes made it less stable.

If the 960 remains stable for a day or so, I may increase the overclock again.  For some reason, I had difficulty launching DJM34's Windows binary at default intensity, or my former setting of "-i 16.5" for Lyra2.  The card is mining Lyra2 instead of Quark, and making a big difference in my total Lyra2 hash power.

The card should be mining in the "P0" state, but PrecisionX 16 doesn't have a specific indicator for that.

I also play games with it.         --scryptr

[djm34]

DJM34, SP_ --

I flipped you each a nickle.  Thank you for your hard work!  I hope my 960's will be able to mine Lyra2 on Windows at about 1250kh/s soon, maybe more!

Thanks!       --scryptr

P.S.  I was able to get DJM34's Windows binary to run on my Win 7 x64 system with a 2GB GTX960 SSC with ONLY the performance setting of "-i 16.3".  No other performance settings were used.  Algo, username, password were as standard.

Result:  1175kh/s mining Lyra2       --scryptr

thanks,
don't forget to run at p0 state using nvidia-smi , that gives the possibility to oc the memclock (it will run also at a somewhat)

From what I've seen memory OCs aren't worth it. They give you a tiny bit of extra hash and they wreck your efficiency. Like 5% more hashrate for 15% more power.

well they are for memory hard algo as it decreases the frame buffer usage... (meaning less bottleneck at that level)
and if you have a large number of cards, you probably want a moderate power usage, if you are limited in gpu ressource you want to get the highest hashrate

OVERCLOCKING--

I am running DJM34's Windows binary with an intensity setting of "-i 16.3"' and +100 core / +300 mem overclock utilizing EVGA PrecisionX 16.  The result is 1200kh/s on my single 2GB GTX 960 SSC.  I earlier reported 1175kh/s with a lower overclock of +80/+240.  The overclock of +100/+300 was the highest stable overclock when mining Quark, but recent Quark code changes made it less stable.

If the 960 remains stable for a day or so, I may increase the overclock again.  For some reason, I had difficulty launching DJM34's Windows binary at default intensity, or my former setting of "-i 16.5" for Lyra2.  The card is mining Lyra2 instead of Quark, and making a big difference in my total Lyra2 hash power.

The card should be mining in the "P0" state, but PrecisionX 16 doesn't have a specific indicator for that.

I also play games with it.         --scryptr

default intensity is set per compute version... since my compute_52 is a 980 with 4gb of memory it works well... obviously with a 960 with only 2GB, it might not work, it should use the same setting as the 750ti
p0 state are shown in nvidia inspector. (however if you didn't changed it, it is most likely running at p2, issue for all the 900 cards), and the mem oc is probably not passed at all

I think there is an option in latest sp version (on which my release is based actually) to set p0 state (haven't tried though...), I used the command line

[sp_]

The Lyra2 profit has dropped alot.
1 week ago The rental sites payed 1.3 BTC/Day for 1 gigahash of lyra.
today it's down to 0.6-0.8BTC/Day