New build with more hashing power in most algos.
GTX 750 1480core/1567mem testing with --cpu-priority 5 on yaamp: X15 faster 8-10khs X14 faster 8-10khs X13 faster 8-10khs X11 - BROKEN!!! start /realtime ccminer.exe -a x11 --cpu-priority 5 -o stratum+tcp://yaamp.com:3533 -u X -p x *** ccminer 1.5.39-git(SP-MOD) for nVidia GPUs by sp-hash@github ***
Built with VC++ 2013 and nVidia CUDA SDK 6.5
Based on pooler cpuminer 2.3.2 and the tpruvot@github fork
CUDA support by Christian Buchner, Christian H. and DJM34
Includes optimizations implemented by sp , klaust, tpruvot and tsiv.
[2015-02-15 14:45:41] CPU priority: realtime
[2015-02-15 14:45:41] Starting Stratum on stratum+tcp://yaamp.com:3533
[2015-02-15 14:45:41] NVAPI GPU monitoring enabled.
[2015-02-15 14:45:41] 1 miner thread started, using 'x11' algorithm.
[2015-02-15 14:45:42] Stratum difficulty set to 0.016
[2015-02-15 14:45:42] yaamp.com:3533 x11 block 220530
[2015-02-15 14:45:55] yaamp.com:3533 x11 block 220530
[2015-02-15 14:45:55] GPU #0: GeForce GTX 750, 8370 kH/s
[2015-02-15 14:46:05] yaamp.com:3533 x11 block 186310
[2015-02-15 14:46:06] GPU #0: GeForce GTX 750, 8410 kH/s
high hashrate and no "ya" |
|
|
|
R38 cubit works no problem on yaamp and hamsterpool. Only 4340khs on my poor gtx750  |
|
|
|
Question about CUDA 6.5 Toolkit - when I install this, it wants to downgrade my driver from 347.xx, do I have to allow this, or will it function with my current drivers?
You can keep your recent driver. But nVidia CUDA installer often changes driver despite the user choice. In that case you will need to reinstall your favorite driver. |
|
|
|
Also, added cpu priority and affinity control, in response to the problems with ccminer If you have CPU miners set-up, use "priority":"BelowNormal" in their algo config to prevent lockups. ccminer, for Nvidia, likes "RealTime", but beware of these notes: Note 1: Realtime by minercontrol is only possible when giving administrator privileges to minercontrol (also accounts for everyone using different miners) Note 2: --cpu-priority by ccminer overrides minercontrols priority Note 3: When giving administrator privileges to minercontrol and setting the priority by minercontrol to something DIFFERENT than what's used by --cpu-priority by ccminer, then your whole system locks up Note 4: In general, it's best to avoid making the miner set its own priority and affinity and let minercontrol do it. Thank you very much! I put both "priority": "RealTime" and --cpu-priority 5 to config and it works! |
|
|
|
It works in tpruvot/Epsylon3s fork to set realtime priority, not in SP_s or Schleicher/KlausT. Better to ask those last two/three  Latest releases from SP do have --cpu-priority. But I mean is there a way to make Miner Control to start miner with /realtime option? |
|
|
|
|
Thanx for new release! It works. quark performance is nearly the same with r36 abd r37.
One moment - i don't now if it worth to point at - x13 don't work on default settings on Hamsterpool.
It works fine on Yaamp and Nicehash though ... )))
|
|
|
|
|
Is there any way to start miner in real-time priority? Like "start /realtime ccminer.exe"
I know that recent ccminers have --cpu-priority feature but I want to have a main thread in realtime to. Now it shows medium priority in Task manager even if I start with --cpu-priority 5 option
|
|
|
|
1.5.36(sp-MOD) is available here: (5-feb-2015)
...
Post your stats here. Card name/gpu clock/memclock
gtx 750 (1470gpu/1550mem) x11 2847 khs quark 5610 khs lyra 853 khs fresh 3435 khs x13 don't work x14 2200 khs x15 1920 khs note: some of my prev records was with more oc |
|
|
|
1.5.36(sp-MOD) is available here: (5-feb-2015)
fixed x11
you removed "h_found[thr_id][0] = 0xffffffff;" from x11.cu but added foundNonce = 0xffffffff;
if (foundNonce != 0xffffffff)
...
to x13.cu x13 don't work now as far as i see ... |
|
|
|
Mind you Nvidia Maxwell have Lyra2 to themselves, 700khs per card. To be competitive, it would need to hit around 2.1mhs on a R9 290  Only joking  860khs on slightly overclocked gtx750 (without TI) |
|
|
|
i love it )))  |
|
|
|
try to remove this commit. (the MyStreamSynchronize calls) https://github.com/sp-hash/ccminer/commit/40858b1e817c4ea40cf254fe292b3a3c7ca328f2I think quark will be faster, but your computer will be slow an unusable if you use the graphic card for other work. The syncronization code was added between release 31 and 32 int the latest versions (release 33 and up) it is also possible to increase the cpu usage for more hash. This was feature was merged from the tpruvot/ccminer fork. --cpu-affinity set process affinity to specific cpu core(s) mask --cpu-priority set process priority (default: 0 idle, 2 normal to 5 highest) try --cpu-priority 5 my display is attached to built-in graphics, so this is not a problem. I will give it a try And i always run ccminer with realtime priority. After --cpu-priority appearing i use it too. upd: strange ... i didn't find "MyStreamSynchronize(NULL, 4, thr_id)" on line 237 or nearby in the quarkcoin.cu. Lines "MyStreamSynchronize(NULL, 1, thr_id)" "MyStreamSynchronize(NULL, 2, thr_id)" "MyStreamSynchronize(NULL, 3, thr_id)" was found and commented. Now building ... upd2: you are a wizard A new quark record for my poor GTX750 - 5650KH, better then R31 |
|
|
|
This code will force the kernal to use 64 registers. bether on the 750ti worse on the 970/980. What I usually do is to case on the compute version and run different configurations for different compute version. I think many of the kernals haven't been tweaked for a while, and hash can be gained. If you see my Bitcoin change, all I did was to change the kernal launch configutration for a 17% speedup. here is the commit: https://github.com/sp-hash/ccminer/commit/c79f622969393f52f3462e2c3e967777cae1d7d3thanks for explanation R35 after this few mods is best for me, maybe except for quark (r31 is 20-30 kh better), but it's a matter of measurement error |
|
|
|
Yes, i put back those "__global__ __launch_bounds__(256, 4)" etc and got some near measurement error gain of ~20kh |
|
|
|
Ahh, I found the problem now
remove the line
h_found[thr_id][0] = 0xffffffff;
in x11.cu
yeah, the next line "if (h_found[thr_id][0] != 0xffffffff)" is slightly not compatible with it upd: now it works. ~2850 kh (the same speed as in r31 & r32) |
|
|
|
Seems to work for others. (yaamp.com)
Wich algos are broken? Did you try fresh or quark? Might be an issue with cuda 7.0 (wich is only released in beta version)
only x11 is broken. All others work fine. I compiled with cuda 6.5 preset (as default). Cuda 7 installed is not an issue. You should recheck a code. I didn't see any working Release 35 clients on yaamp's x11 stats ... |
|
|
|
Strange, it works here.
Make sure you have the latest driver.
I might have copied the wrong exe file though. If you build it from github it should work.
just recompiled. The same. No accepts. No boos. Driver is from CUDA 7.0 pack as always 347.12 Previous releases run x11 normally |
|
|
|
X11 on Release35 doesn't seem to work on my 750ti. Looks like its running but no shares submitted to pool. Tested with Coinking, Nicehash & YAAMP.
+1 on gtx750 with yaamp. crunching but no accepted shares (yays or boos) |
|
|
|
Gtx 750 has only got 1GB of memory. I will lower the default intensity for lyra2 on compute 5.0
Thanx for the reply. I tried to play with intensity -i parameter and found that Release 34 works for my GTX750 up to 20.3 value. I think it's not a memory issue, gpu-z shows very small memory load but the fact that simple 750 has less CUDA cores - only 512 instead of 640 750ti has ... |
|
|
|
|
Show Posts
