I'm looking forward to moving to CUDA 7.0, especially if it produces more hash. --scryptr
sp_ ccminer compiled with CUDA 7.0 produces incorrect hash ... i tried it some time ago on windows |
|
|
|
another great work sp_ and co  gtx750 Commit 742 X11 @ 2890 khs from 2890 Skein @ 83620 khs from 75500 Quark @ 5824 khs from 5810 |
|
|
|
How much x11 hash for GTX 680 2gb ?
this thread is for maxwell 5.0 or later GPUs ... |
|
|
|
Palit GTX750 1gb (1480/1568) Commit 737 Skein @ 75500 khs from 73000 on previous release  |
|
|
|
Good suggestions, but I should note that it does the same thing on stock clocks. And I can use release 44 with no issues but I WANT THE BOOST!  But, I will look further into it, and I may flash the BIOS, but I never had to with my 750Ti, so I don't want to unless I need to. Try to decrease clocks significantly below standard. If the problem remains then this is not a clock/power consumption problem. P.S. Did you try benchmark mode? Is situation the same? |
|
|
|
Release 46 doesn't perform well on my machine, (GTX 970 / Win 8.1 x64) mining Quark algo, no settings.
The power consumption is a sawtooth waveform. It loads the card to ~120% (overclocked) and then down to basically 0%. Over and over. Up down, up down, up down.
Mining XMR the power consumption might fluctuate a little, and might not load all the way near 100%, but it is at least never below 60%.
I don't know why this happens and I know sp_ works hard on it and most you guys are on linux, but it sucks for me.
It maybe you card/driver problem. If power consumption goes over 100% TDP then card goes to some low power mode. And again, and again, and again. Try to decrease clocks or maybe you will need to flash bios with higher TDP. I did it on my gtx750 cause by default its TDP was only 38W and it went "resting" on every serious load. |
|
|
|
submitted faster blake with one thread. Please test and report.
run quark with no launch parameters.
all I can say is WOW. Just built and run quark without any parameters. Hashrate goes from R43 record 5717 to stable 5810. GPU memory usage raised from 112mb to 383mb Power consumption is also raised up to 63% TDP from max 58% of release 43. (gtx 750@1480/1570) Just need some time to check pool hashrate |
|
|
|
What the best settings -g and -i for single 750 ti?
Do you mean Quark? My guess is ccminer by sp_ release 43 (thai build ) without any -g or -i parameters. Or maximum -i that doesn't crash I have no faith in multiple gpu threads ... For other algos use Release 44 or 45 without -g with manually tuned -i or default -i |
|
|
|
The as-compiled by sp_ release 45 is a nightmare on my rig, mining Quark GTX 970 i7 4770 16GB Win 8.1 Unsteady hashrate with -i 20, and most any other intensity setting crashes. After a crash, the GPU goes into a low power mode and I have to restart the machine. I suspect that if I used an older version of Afterburner or Precision X that has the K-Boost button, I might be able to wake it up after the crash without restarting . Either way, it is very buggy and that makes me  download nvidia inspector Use bat-file with nvidiaInspector -restartDisplayDriver |
|
|
|
try with -d 0,0 . is the total hashrate correct?
Nope, it shows higher hashrate then my favorite Release43 but it doesn't confirm by the pool. |
|
|
|
I think the problem is that you are using the 750 (512 shaders, 1gb memory) card. The card is out of resources, and is unable to increase the speed with more threads.
So why miner stats show high hashrate? You should fix it I think. If you will fix the stats you will see real situation with performance. |
|
|
|
What cpu's are you running with? How many cores?
It's old athlon 64 x2 dual core running 3ghz |
|
|
|
|
All this threading is just playing with numbers, pools show real performance drop ...
|
|
|
|
[2015-04-21 20:23:02] GPU #0: GeForce GTX 750, 4110 kH/s
[2015-04-21 20:23:02] GPU #0: GeForce GTX 750, 555.39 kH/s
[2015-04-21 20:23:03] yaamp.com:4733 qubit block 485
[2015-04-21 20:23:03] GPU #0: GeForce GTX 750, 4178 kH/s
[2015-04-21 20:23:03] GPU #0: GeForce GTX 750, 357.77 kH/s
[2015-04-21 20:23:07] GPU #0: GeForce GTX 750, 4145 kH/s
[2015-04-21 20:23:07] accepted: 13/13 (100.00%), 5792 khash/s yay!!!
[2015-04-21 20:23:08] yaamp.com:4733 qubit block 486
[2015-04-21 20:23:08] GPU #0: GeForce GTX 750, 404.75 kH/s
[2015-04-21 20:23:08] GPU #0: GeForce GTX 750, 4067 kH/s
[2015-04-21 20:23:12] GPU #0: GeForce GTX 750, 4105 kH/s
[2015-04-21 20:23:12] accepted: 14/14 (100.00%), 5799 khash/s yay!!!
[2015-04-21 20:23:22] GPU #0: GeForce GTX 750, 4120 kH/s
[2015-04-21 20:23:23] accepted: 15/15 (100.00%), 5802 khash/s yay!!!
[2015-04-21 20:23:25] GPU #0: GeForce GTX 750, 4114 kH/s
[2015-04-21 20:23:25] accepted: 16/16 (100.00%), 5801 khash/s yay!!!
[2015-04-21 20:23:27] yaamp.com:4733 qubit block 486
[2015-04-21 20:23:27] GPU #0: GeForce GTX 750, 679.92 kH/s
[2015-04-21 20:23:27] GPU #0: GeForce GTX 750, 4084 kH/s
[2015-04-21 20:23:34] yaamp.com:4733 qubit block 487
[2015-04-21 20:23:34] GPU #0: GeForce GTX 750, 4114 kH/s
[2015-04-21 20:23:34] GPU #0: GeForce GTX 750, 417.11 kH/s
[2015-04-21 20:23:38] GPU #0: GeForce GTX 750, 4142 kH/s
[2015-04-21 20:23:39] accepted: 17/17 (100.00%), 5806 khash/s yay!!! this is qubit on my single gtx750 with release 45 ccminer.exe --cpu-priority 5 -d 0,0 -i 16 -a qubit But I'm not sure that this numbers are real performance ... |
|
|
|
|
The only reason I see for running more threads then physical C(G)PUs is to fill the gaps between tasks. You can easily see that gaps on GPU-Z load graph. In other cases it is useless I think. There is a case in some memory intensive applications when running multiple threads on single CPU gives boost over single thread. But this is a case when single-threaded app is bad coded not fitting data in cache.
|
|
|
|
The anomalous "GPU #11" represents one of the threads, but generally the output only displays GPUs #0-5. As you can see, the acceptance rate, while mining Quark with v45, is still good. --scryptr
did the pool confirm the numbers that miner shows? I mean hashrate ... I tried with my single card with -d 0,0 option and it gives (sometimes but rather often) 'does not validate on CPU' for non-existing GPU1. Also higher hashrate the miner shows is not confirmed by the pool. |
|
|
|
sp_ I confirm that built from your github source pre-release 45 gives 4540khs instead of the best previous 4418khs of r43. R44 was no good for me except whirpool and x15. Quark seems to be very close to R43 record 5717khs but R43 still better for quark oced 750non-ti 1gb, comparing v43 vs. v44 for my gtx750(non-ti) (windows binaries from github)
x15: 1966 vs 1976
x13: 2272 vs 2270
x11: 2886 vs 2883
quark: 5700 vs 5660
qubit: 4418 vs 4419 (with drops)
lyra: 882 vs 881
So, only x15 gain for me |
|
|
|
I have made this possible. Over a period of 6 months ppl have donated around 2 btc for my hard work. But a
amd kernal that is 300% faster can be sold for way more than 2 btc. My gpu coder student time is over. Time to make some $$$
It was a joke. My interest in mining is only in the ways how code for specific devices can be optimized. To few places are in the world where developers care about optimization ))) That's why i don't like private kernels, i can't see the code ((( |
|
|
|
I have studied the opencl code of sgminer, and I see many possible speed increases. Quark/qubit. I have picked up a couple of AMD cards cheap(280x,290 and 290x), and will try to
rewrite and optimize quark and qubit. I belive 10-15 MHASH quark per card is possible on the 280x (up from todays 5MHASH)
300% faster.
it's not fair ))) quark is last nvidia shelter ))) |
|
|
|
|
release 43 is way faster. No need to play with 42
|
|
|
|
|
Show Posts
