Author

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

legendary
Activity: 1154
Merit: 1001
Concerning the cards with more than 2GB, I think there is also some limitation in the driver layer (WDDM), 2.3GB or thereabouts is the maximum that Windows can use with regular display drivers. FWIW, I know the maximum VRAM I've used in Linux is about 3.7GB per card.

Windows 10 might be finally addressing this though (eventually):
GPU virtual memory in WDDM 2.0

What is your hashrate in linux with scrypt-n?

I've never tested Scrypt-N at all, ever, so I am not familiar with the right settings for this one. If I have a chance I'll run some autotune/benchmarking and let you know.
sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
I assume this is x11?

Try with -i 20.9 or -i 20.8 and -g 2

-g 2 (2 threads) will actually increase the intensity by 1 but split the memory allocation into 2 blocks instead of one big block of memory. In windows 8 it seems to be a problem to allocate big chunks of continious gpu memory.


What is the rate when you don't have a -i parameter?
sr. member
Activity: 285
Merit: 250
I used to be able to get over 10000 KH and intensity 21 on a GTX 980
the latest version crashed at intensity 21 and at 20 it can't go over 9000
legendary
Activity: 1764
Merit: 1024
Upgrading the driver to the latest version is a good idea. NVIDIA fixed some memory allocation bugs.
With the older drivers, ccminer sometimes got out of memory even if there where alot of free memory on the cards.
Restarting the miner helped, but the crashes seamed to be random.


Windows 7 seems to be bether in allocating big blocks of memory on the gpu. In windows 8 there is some kind of restriction.. I have problems with the cryptonight miner to run with optimal settings.


On windows:

Since all my builds are 32 bit (faster hashing) you might want to increase the allowed memory in the application from 2gb to 3gb with this command:

editbin /LARGEADDRESSAWARE ccminer.exe

I will modify the project file tonight so that this flag is set automaticly in all future builds.

I don't recall Claymore running into this, you may want to talk to him. He might have a idea of how to get around it or figure it out, unless this is a Nvidia only issue.
hero member
Activity: 677
Merit: 500
OK. Then i download and test on win 10...
sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
Upgrading the driver to the latest version is a good idea. NVIDIA fixed some memory allocation bugs.
With the older drivers, ccminer sometimes got out of memory even if there where alot of free memory on the cards.
Restarting the miner helped, but the crashes seamed to be random.


Windows 7 seems to be bether in allocating big blocks of memory on the gpu. In windows 8 there is some kind of restriction.. I have problems with the cryptonight miner to run with optimal settings.


On windows:

Since all my builds are 32 bit (faster hashing) you might want to increase the allowed memory in the application from 2gb to 3gb with this command:

editbin /LARGEADDRESSAWARE ccminer.exe

I will modify the project file tonight so that this flag is set automaticly in all future builds.
sr. member
Activity: 506
Merit: 252
Concerning the cards with more than 2GB, I think there is also some limitation in the driver layer (WDDM), 2.3GB or thereabouts is the maximum that Windows can use with regular display drivers. FWIW, I know the maximum VRAM I've used in Linux is about 3.7GB per card.

Windows 10 might be finally addressing this though (eventually):
GPU virtual memory in WDDM 2.0

What is your hashrate in linux with scrypt-n?
legendary
Activity: 1154
Merit: 1001
Concerning the cards with more than 2GB, I think there is also some limitation in the driver layer (WDDM), 2.3GB or thereabouts is the maximum that Windows can use with regular display drivers. FWIW, I know the maximum VRAM I've used in Linux is about 3.7GB per card.

Windows 10 might be finally addressing this though (eventually):
GPU virtual memory in WDDM 2.0
hero member
Activity: 750
Merit: 500
the interactive option also is made for that... i guess interactive should be checked instead of is_windows()

Would love to see this change made! I was getting quite frustrated with mining scrypt-jane and the card not allocating anywhere near the amount of memory it could have (not running a display off the card).
sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
Here is a tip for you. Delete the error.log file in the ccminer folder, it can get huge after a while.
legendary
Activity: 1484
Merit: 1082
ccminer/cpuminer developer
the interactive option also is made for that... i guess interactive should be checked instead of is_windows()
sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
Edit: 200 pages! Congrats and keep up the good work sp_ (sent a few beers your way).

Thanks alot Smiley
legendary
Activity: 1154
Merit: 1001
See if I can post it tomorrow...but Scrypt-Jane:15 I get 1.24 mh per 750ti if that's any help for now.

Unfortunately that doesn't help, as I really don't recall Scrypt-Jane:15 performance on the 750ti at all (and neither can I test it). All of my performance & test references are on Scrypt-Jane:16 specifically. Thanks for posting though!

0.38 khash (750ti 2GB, win 7)
but only 1.05 GB vram is in use ...

I'm particularly curious about Vista, as memory management differences might explain better performance on that one.

[...] So a 750ti with 2 GB is hashing as fast as a 750ti 4 GB at scrypt-n (chacha) algos.
(970 4 GB allocates a max of 2.1 GB, above that = performance drop) [...]

I find that statement to be true for Windows (7 & 8, still dunno about Vista), but not for Linux. On Linux, you can use different launch settings for the 4GB cards and much better performance can be achieved. My 980's run fastest with about 3.4 GB of VRAM allocated, but only on Linux. Might relate to the memory backoff settings discussed up-thread.

device_backoff = is_windows() ? 12 : 2;
Windows backoff 12%, non-Windows backoff 2%

device_backoff = is_windows() ? 1 : 2;
Windows backoff 1%, non-Windows backoff 2%

I suppose this is the change. Have not done this modification myself before though.
legendary
Activity: 3164
Merit: 1003
For scrypt based coins ccminer is set to only use 88% of the maximum video RAM in case of Windows and 98% in case of Linux by default:

Code:
device_backoff[i] = is_windows() ? 12 : 2;

It is there for safety so it won't crash for people who wish to mine on their main card.
One of the changes I always do before compiling is to change that value to 1 for Windows to allow it to use 99% of memory and if you don't have a monitor attached to your card and not running something that is using VRAM needlessly, it won't crash. Not even while autotuning.


I used that since cudaminer days so I have no idea about the hashrate difference anymore.


Now that we're entering the territory of cards with 3GB+ video memory it's worth noting that 32-bit ccminer can't utilize more than 3GB.
64-bit can utilize it all but 64-bit is also noticeably slower so for cards like the 970 it doesn't worth it but for the 980 Ti it might - for algos that scale with memory amount (not access) like Scrypt-Jane.
Afaik, 32-bit softwares can actually utilize more than 3GB video memory but only if the data is also stored in the system RAM which is generally not optimal for mining.

Edit: 200 pages! Congrats and keep up the good work sp_ (sent a few beers your way).
How does one apply that?

device_backoff = is_windows() ? 12 : 2;

thx


Format for the ternary operator is expression ? if_true : if_false;
Being a noob at this....I better leave this alone.
Thx  Wolf0  Smiley

EDIT: Just curious how one goes about this.
legendary
Activity: 3164
Merit: 1003
For scrypt based coins ccminer is set to only use 88% of the maximum video RAM in case of Windows and 98% in case of Linux by default:

Code:
device_backoff[i] = is_windows() ? 12 : 2;

It is there for safety so it won't crash for people who wish to mine on their main card.
One of the changes I always do before compiling is to change that value to 1 for Windows to allow it to use 99% of memory and if you don't have a monitor attached to your card and not running something that is using VRAM needlessly, it won't crash. Not even while autotuning.


I used that since cudaminer days so I have no idea about the hashrate difference anymore.


Now that we're entering the territory of cards with 3GB+ video memory it's worth noting that 32-bit ccminer can't utilize more than 3GB.
64-bit can utilize it all but 64-bit is also noticeably slower so for cards like the 970 it doesn't worth it but for the 980 Ti it might - for algos that scale with memory amount (not access) like Scrypt-Jane.
Afaik, 32-bit softwares can actually utilize more than 3GB video memory but only if the data is also stored in the system RAM which is generally not optimal for mining.

Edit: 200 pages! Congrats and keep up the good work sp_ (sent a few beers your way).
How does one apply that?

device_backoff = is_windows() ? 12 : 2;

thx
sr. member
Activity: 506
Merit: 252
@tbearhere

Can you post your hashrate/card for Scrypt-Jane:16 on Vista? Would be funny to find that Vista matches the performance on Linux (or betters it?), while recent Windows versions all suck!  Roll Eyes


0.38 khash (750ti 2GB, win 7)
but only 1.05 GB vram is in use ...
sr. member
Activity: 506
Merit: 252
For scrypt based coins ccminer is set to only use 88% of the maximum video RAM in case of Windows and 98% in case of Linux by default:

Code:
device_backoff[i] = is_windows() ? 12 : 2;

It is there for safety so it won't crash for people who wish to mine on their main card.
One of the changes I always do before compiling is to change that value to 1 for Windows to allow it to use 99% of memory and if you don't have a monitor attached to your card and not running something that is using VRAM needlessly, it won't crash. Not even while autotuning.


I used that since cudaminer days so I have no idea about the hashrate difference anymore.


Now that we're entering the territory of cards with 3GB+ video memory it's worth noting that 32-bit ccminer can't utilize more than 3GB.
64-bit can utilize it all but 64-bit is also noticeably slower so for cards like the 970 it doesn't worth it but for the 980 Ti it might - for algos that scale with memory amount (not access) like Scrypt-Jane.
Afaik, 32-bit softwares can actually utilize more than 3GB video memory but only if the data is also stored in the system RAM which is generally not optimal for mining.

Edit: 200 pages! Congrats and keep up the good work sp_ (sent a few beers your way).

cudaminer allocates a maximum of 1.05 GB for scrypt-n (chacha) on my 750ti cards. If you use settings which allocate beyond that 1.05 GB the miner slows down considerably.

eg. I had a chance to try to mine with a 750ti 4gb !!! but any settings above 1.05 GB killed the performance.

So a 750ti with 2 GB is hashing as fast as a 750ti 4 GB at scrypt-n (chacha) algos.
(970 4 GB allocates a max of 2.1 GB, above that = performance drop)

For team red yacminer is very neat because you can tweak/allocate every single megabyte of vram which lets you set a lower lookup gap and higher intensity.
legendary
Activity: 3164
Merit: 1003
@tbearhere

Can you post your hashrate/card for Scrypt-Jane:16 on Vista? Would be funny to find that Vista matches the performance on Linux (or betters it?), while recent Windows versions all suck!  Roll Eyes
See if I can post it tomorrow...but Scrypt-Jane:15 I get 1.24 mh per 750ti if that's any help for now.
legendary
Activity: 2002
Merit: 1051
ICO? Not even once.
For scrypt based coins ccminer is set to only use 88% of the maximum video RAM in case of Windows and 98% in case of Linux by default:

Code:
device_backoff[i] = is_windows() ? 12 : 2;

It is there for safety so it won't crash for people who wish to mine on their main card.
One of the changes I always do before compiling is to change that value to 1 for Windows to allow it to use 99% of memory and if you don't have a monitor attached to your card and not running something that is using VRAM needlessly, it won't crash. Not even while autotuning.


I used that since cudaminer days so I have no idea about the hashrate difference anymore.


Now that we're entering the territory of cards with 3GB+ video memory it's worth noting that 32-bit ccminer can't utilize more than 3GB.
64-bit can utilize it all but 64-bit is also noticeably slower so for cards like the 970 it doesn't worth it but for the 980 Ti it might - for algos that scale with memory amount (not access) like Scrypt-Jane.
Afaik, 32-bit softwares can actually utilize more than 3GB video memory but only if the data is also stored in the system RAM which is generally not optimal for mining.

Edit: 200 pages! Congrats and keep up the good work sp_ (sent a few beers your way).
legendary
Activity: 1154
Merit: 1001
@tbearhere

Can you post your hashrate/card for Scrypt-Jane:16 on Vista? Would be funny to find that Vista matches the performance on Linux (or betters it?), while recent Windows versions all suck!  Roll Eyes
Jump to: