CCminer(SP-MOD) Modded GPU kernels.

[myagui]

Or maybe on windows it's different...

Yeps. On Windows it is extremely simple to set fixed clocks, fans, overclocking, so you can easily have a "benchmark platform".

With a headless Linux system I don't think there's any solution for fixed fans yet, others might know differently. I previously had fixed fans and clocks on Linux, but I perfectly recall that I specifically had to configure/attach a monitor in order to get that working at the time.

[sp_]

I must say that I didn't have any problem benchmarking amd cards: if the room was hot, I'd put the fans at high speed, run the miner and wait a couple minute to stabilize, and that's it. I could make 100 changes to a kernel in a day and check them all, accurately.

On nvidia I have throttling problems I can't easily fix (the cards reduce clock speed in a number of situations I just can't predict), overclocking/downclocking is more difficult as the cards tend to change clocks by themselves, and the hashrates fluctuates wildly, and even changes between ccminer runs.
The rig is headless so I only have nvidia-smi to work with, and it can't set the fan speed.
So when I make a little kernel speedup, I spend more time benchmarking it (to be sure it's indeed an improvement), than making the improvement itself :-/
Maybe there are some nvidia-smi settings to make it more stable?
Or maybe on windows it's different...
Finally I may need a workstation with a nvidia as main card, and work on it.

Buy another 970 card. The gigabyte windforce oc never trottle and mines on a stable clockrate. easy to verify speedups. For very small changes, taka a look at the generated PTX assembly code, less code lines is bether but not always..
You can also test your chances on a big rig with many cards, If you have many cards small speedups of 0-1 KHASH per card can be visible.

To finance the cards, you can hope that you will ROI the cards in 1 year by increasing the speed of the kernals

[Slava_K]

TPB52 7 is best for mining. My gtx 980 make 11.2-11.6 Mh. 960 gtx make 6 Mh. Super!
For rig (2x980+1x960) hash is 28500!
PS. It is LYRA2v2! +100 git 1052 works!

[sp_]

These settinge should be taken out of the hardcoded kernal and be adjustable in the commandline. Like in scrypt.   -l 7x19 (7threads per block with -X intensity 19).
Because on the 970 9 seems to be bether.

[Slava_K]

Ok! Thanks.

[bensam1231]

I must say that I didn't have any problem benchmarking amd cards: if the room was hot, I'd put the fans at high speed, run the miner and wait a couple minute to stabilize, and that's it. I could make 100 changes to a kernel in a day and check them all, accurately.

On nvidia I have throttling problems I can't easily fix (the cards reduce clock speed in a number of situations I just can't predict), overclocking/downclocking is more difficult as the cards tend to change clocks by themselves, and the hashrates fluctuates wildly, and even changes between ccminer runs.
The rig is headless so I only have nvidia-smi to work with, and it can't set the fan speed.
So when I make a little kernel speedup, I spend more time benchmarking it (to be sure it's indeed an improvement), than making the improvement itself :-/
Maybe there are some nvidia-smi settings to make it more stable?
Or maybe on windows it's different...
Finally I may need a workstation with a nvidia as main card, and work on it.

Buy another 970 card. The gigabyte windforce oc never trottle and mines on a stable clockrate. easy to verify speedups. For very small changes, taka a look at the generated PTX assembly code, less code lines is bether but not always..
You can also test your chances on a big rig with many cards, If you have many cards small speedups of 0-1 KHASH per card can be visible.

To finance the cards, you can hope that you will ROI the cards in 1 year by increasing the speed of the kernals

Yeah the one plus side to the Gigabyte cards is they never seem to throttle and clock the highest. Of course they use like 10-15% more power then all the other cards, so...

[sp_]

Yeah the one plus side to the Gigabyte cards is they never seem to throttle and clock the highest. Of course they use like 10-15% more power then all the other cards, so...

As I said, my Zotac card start to mine quark at 15.5 mhash, and then it trottles and fall down to 13.5-14. My gigabyte is stable at 17MHASH. 3,5 MHASH bether.

http://www.zotac.com/products/graphics-cards/geforce-900-series/product/geforce-900-series/detail/geforce-gtx-970.html

The zotac card is much smaller and heats up faster.

[pallas]

Yeah the one plus side to the Gigabyte cards is they never seem to throttle and clock the highest. Of course they use like 10-15% more power then all the other cards, so...

As I said, my Zotac card start to mine quark at 15.5 mhash, and then it trottles and fall down to 13.5-14. My gigabyte is stable at 17MHASH. 3,5 MHASH bether.

http://www.zotac.com/products/graphics-cards/geforce-900-series/product/geforce-900-series/detail/geforce-gtx-970.html

The zotac card is much smaller and heats up faster.

I have an msi 970 that is more stable than the others, but still it starts at 16.5 and goes down to 16 after a while.
Well, I may get a gigabyte or just wait for the winter ;-)

[Slava_K]

Asus Strix 980GTX 20.8 Mh Quark 1380 MHz.

[myagui]

These settinge should be taken out of the hardcoded kernal and be adjustable in the commandline. Like in scrypt.   -l 7x19 (7threads per block with -X intensity 19).
Because on the 970 9 seems to be bether.

@sp_:
Shouldn't the optimal blocks/threads values always be relative to the number of SMM/SMXs in any given card? It might be possible to have ccminer automatically detect - and adjust - to the number of SMM/SMXs on the available cards, and then just use the intensity parameter for the fine tuning.

I lost this bit of information somewhere along the thread history, but seeing as you now have -X , is -i still doing anything on your fork? If both parameters can be used, what the F#%@ is each one doing? Thanks for clearing this up 

It's starting to look a bit mad to find the best settings for one's card, if there are 3 distinct parameters to tune (-X, -i, -l).

[badgoes]

Or maybe on windows it's different...

Yeps. On Windows it is extremely simple to set fixed clocks, fans, overclocking, so you can easily have a "benchmark platform".

With a headless Linux system I don't think there's any solution for fixed fans yet, others might know differently. I previously had fixed fans and clocks on Linux, but I perfectly recall that I specifically had to configure/attach a monitor in order to get that working at the time.

to set the fan on linux just test this

https://gist.github.com/squadbox/e5b5f7bcd86259d627ed

[t-nelson]

These settinge should be taken out of the hardcoded kernal and be adjustable in the commandline. Like in scrypt.   -l 7x19 (7threads per block with -X intensity 19).
Because on the 970 9 seems to be bether.

@sp_:
Shouldn't the optimal blocks/threads values always be relative to the number of SMM/SMXs in any given card? It might be possible to have ccminer automatically detect - and adjust - to the number of SMM/SMXs on the available cards, and then just use the intensity parameter for the fine tuning.

Seems reasonable.  I don't think we can directly query the physical configuration of the chipset.  But it wouldn't be much to maintain a LUT.  The major hurdle would probably be reliably parsing the compilation output for the kernel.

[myagui]

I remember getting the number of SMM/SMXs in the CryptoNight miner... can't remember how, though.

Yep. TSIV's Cryptonight ccminer complains whenever the blocks/threads (don't recall which one now) is not a multiple of the SMX/SMM on the card. IIRC, it does this also accurately for cards that did not exist when it was released, so the approach is not LUT based.

[pallas]

Or maybe on windows it's different...

Yeps. On Windows it is extremely simple to set fixed clocks, fans, overclocking, so you can easily have a "benchmark platform".

With a headless Linux system I don't think there's any solution for fixed fans yet, others might know differently. I previously had fixed fans and clocks on Linux, but I perfectly recall that I specifically had to configure/attach a monitor in order to get that working at the time.

to set the fan on linux just test this

https://gist.github.com/squadbox/e5b5f7bcd86259d627ed

Thanks, but I fear it needs a monitor or the x session will not start... Or will it?

[joblo]

Or maybe on windows it's different...

Yeps. On Windows it is extremely simple to set fixed clocks, fans, overclocking, so you can easily have a "benchmark platform".

With a headless Linux system I don't think there's any solution for fixed fans yet, others might know differently. I previously had fixed fans and clocks on Linux, but I perfectly recall that I specifically had to configure/attach a monitor in order to get that working at the time.

to set the fan on linux just test this

https://gist.github.com/squadbox/e5b5f7bcd86259d627ed

Thanks, but I fear it needs a monitor or the x session will not start... Or will it?

Look back about 10 pages in this thread, I got an xsession, OC and fan control on a headless card. Hashbrown
pointed to another thread with a detailed procedure for doing this. Coincidentally it only offers fixed fan settings.
The OC is a fixed offset from the base clock which can throttle.

[badgoes]

Or maybe on windows it's different...

Yeps. On Windows it is extremely simple to set fixed clocks, fans, overclocking, so you can easily have a "benchmark platform".

With a headless Linux system I don't think there's any solution for fixed fans yet, others might know differently. I previously had fixed fans and clocks on Linux, but I perfectly recall that I specifically had to configure/attach a monitor in order to get that working at the time.

to set the fan on linux just test this

https://gist.github.com/squadbox/e5b5f7bcd86259d627ed

Thanks, but I fear it needs a monitor or the x session will not start... Or will it?

i have no monitor connected
but i have a linux 14.04 desktop version

[myagui]

I dug around the Kopiemtu thread for the relevant bits, and seems this is the most important one:
In xorg.conf, just before the coolbits statement:

Code:

Option         "AllowEmptyInitialConfiguration" "True"

If I read right, this is how one sets up fake monitors on headless systems.

This will not work for every driver version. Will probably require this command to setup a fresh xorg.conf if a driver update is needed.

Code:

sudo nvidia-xconfig −−enable-all-gpus

I dunno, since I don't have a Linux system currently to test this on. I'd already been able to setup fake monitors (manually) before, so I know didn't use this at the time, but I did have 1 monitor attached to the 1st GPU, so mine was not a fully headless setup.

Edit: better yet, check the source. Hashbrown looks to be doing good stuff over there! 
https://litecointalk.org/index.php?topic=16800.msg266088#msg266088

Cheers!

[pallas]

Thanks everyone, I'll give all this a try asap.
Hopefully I'll then be able to test small kernel enhancements :-)

[scryptr]

Or maybe on windows it's different...

Yeps. On Windows it is extremely simple to set fixed clocks, fans, overclocking, so you can easily have a "benchmark platform".

With a headless Linux system I don't think there's any solution for fixed fans yet, others might know differently. I previously had fixed fans and clocks on Linux, but I perfectly recall that I specifically had to configure/attach a monitor in order to get that working at the time.

to set the fan on linux just test this

https://gist.github.com/squadbox/e5b5f7bcd86259d627ed

Thanks, but I fear it needs a monitor or the x session will not start... Or will it?

NOT ANY MORE--

If you have one of the latest driver packages, you can use nvidia-config to enable cards without monitors to be adjusted:

"sudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration" (Source: https://bitcointalk.org/index.php?topic=826901.msg12279696#msg12279696)

The numbeer "28" is a bitsum that signifies clocks, fanspeed, and power controls.

This was in this thread, earlier. I think that "-a" and the longer "--allow-empty-initial-configuration" are equivalent. THEY ARE NOT EQUIVALENT!  Command "-a"  = "--enable-all-gpus"  

--scryptr

[Grim]

Final release of CUDA 7.5 toolkit (including some fixes)!