Topic: [XMR] JCE Miner Cryptonight/forks, now with GPU! - page 30. (Read 90807 times)

With the parameterless config I was just really wanting to call different configs for different algos.  I've since tested that and found out it works, which makes my suggestion look ridiculous, haha.  Should've tested that before I posted.

With my test 290x at 1000 core and 1250 mem and worksize 8 ; alpha 64 ; beta 8 ; multi_hash 448 I can only get 530 h/s for heavy.  The bulk of my cards are reference cards and perform better than this one but it's all I can test right now.

Hi, JCE. I need some help from you. In my case b4 version seems more stable, however b6 some gpus can give me more hashrate. But some gpu's can't reach max hashrate in b6 and always different. Please help to checkout where my mistake. Thanks a lot.

rx 580 8GBx8(4pcs Gigabyte Aorus, 4pcs Sapphire Nitro+), win10ltsb, adrenalin 18.6.1, virtual memory 90GB
set FORK=12
"gpu_threads_conf" :
[
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":944 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":944 },
    { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 2, "multi_hash":944 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 2, "multi_hash":944 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 3, "multi_hash":944 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 3, "multi_hash":944 },
    { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 4, "multi_hash":944 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 4, "multi_hash":944 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 5, "multi_hash":944 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 5, "multi_hash":944 },
    { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 6, "multi_hash":944 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 6, "multi_hash":944 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 7, "multi_hash":944 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 7, "multi_hash":944 },
    { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 8, "multi_hash":944 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 8, "multi_hash":944 },
],

ver. 033b4
08:08:14 | Hashrate GPU Thread 0: 560.55 h/s
08:08:14 | Hashrate GPU Thread 1: 560.00 h/s - Total GPU 1: 1120.55 h/s
08:08:14 | Hashrate GPU Thread 2: 565.33 h/s
08:08:14 | Hashrate GPU Thread 3: 565.77 h/s - Total GPU 2: 1131.09 h/s
08:08:14 | Hashrate GPU Thread 4: 553.71 h/s
08:08:14 | Hashrate GPU Thread 5: 549.98 h/s - Total GPU 3: 1103.68 h/s
08:08:14 | Hashrate GPU Thread 6: 580.14 h/s
08:08:14 | Hashrate GPU Thread 7: 578.64 h/s - Total GPU 4: 1158.77 h/s
08:08:14 | Hashrate GPU Thread 8: 561.88 h/s
08:08:14 | Hashrate GPU Thread 9: 564.10 h/s - Total GPU 5: 1125.97 h/s
08:08:14 | Hashrate GPU Thread 10: 555.43 h/s
08:08:14 | Hashrate GPU Thread 11: 555.00 h/s - Total GPU 6: 1110.42 h/s
08:08:14 | Hashrate GPU Thread 12: 574.19 h/s
08:08:14 | Hashrate GPU Thread 13: 574.77 h/s - Total GPU 7: 1148.95 h/s
08:08:14 | Hashrate GPU Thread 14: 568.82 h/s
08:08:14 | Hashrate GPU Thread 15: 567.57 h/s - Total GPU 8: 1136.38 h/s
08:08:14 | Total: 9035.80 h/s - Max: 9060.34 h/s
Max hashrate is reached in ~7 minutes

ver. 033b6
20:13:48 | Hashrate GPU Thread 0: 578.96 h/s
20:13:48 | Hashrate GPU Thread 1: 577.56 h/s - Total GPU 1: 1156.52 h/s
20:13:48 | Hashrate GPU Thread 2: 484.24 h/s
20:13:48 | Hashrate GPU Thread 3: 485.10 h/s - Total GPU 2: 969.33 h/s
20:13:48 | Hashrate GPU Thread 4: 571.78 h/s
20:13:48 | Hashrate GPU Thread 5: 572.38 h/s - Total GPU 3: 1144.15 h/s
20:13:48 | Hashrate GPU Thread 6: 601.14 h/s
20:13:48 | Hashrate GPU Thread 7: 603.49 h/s - Total GPU 4: 1204.63 h/s
20:13:48 | Hashrate GPU Thread 8: 582.62 h/s
20:13:48 | Hashrate GPU Thread 9: 583.82 h/s - Total GPU 5: 1166.43 h/s
20:13:48 | Hashrate GPU Thread 10: 575.81 h/s
20:13:48 | Hashrate GPU Thread 11: 575.35 h/s - Total GPU 6: 1151.15 h/s
20:13:48 | Hashrate GPU Thread 12: 594.01 h/s
20:13:48 | Hashrate GPU Thread 13: 593.27 h/s - Total GPU 7: 1187.28 h/s
20:13:48 | Hashrate GPU Thread 14: 490.98 h/s
20:13:48 | Hashrate GPU Thread 15: 488.96 h/s - Total GPU 8: 979.94 h/s
20:13:48 | Total: 8959.40 h/s - Max: 9159.15 h/s
Max hashrate isn't reached

No problem to compare to SRB or TeamRed, i do it myself often, but on such a precise case, please give both config you use so we can reproduce. And if you used JCE autoconfig, so that's normal, i aim it at safety, not at performance (i don't want to burn your GPU remotely because of an overload).

By the way, i'm getting interresting, yet a bit disapointing, results with the Hybrid miner, I got +3% on my Tahiti on v8. Not the +20% I expected but still welcome. The good news is that it will give a boost to all versions of algos on older cards, the bad is that it doesn't apply to the fast ones, on RX+ it causes a perf regression.

Pausing may cause the hashrate to drop, i know this bug but hadn't had time to fix it yet
workaround: use the watchdog to let the miner restart.

The CPU new features will be backported to the GPU one of course.

parameterless config with parameters?
to use several configs, put several different copies of JCE+serviceconfig.txt in several directories, and use the directory as selector.

GPU stuck log: ok i'll add it.

Nope, it has been added to the doc by a user, through a git pull request. I default to believe people so I accepted the pull request but if it's doubtious, so i remove it for now. I admit the value 256 for alpha looked Strange. Please retry with a more normal config (alpha=64, beta=8)

edit: i removed it and put a best config for RX550 instead.

It looks like the pause function has some bug:

I was mining HXV (CN Heavy) with the 0.33b6, with two RX 570 and a Ryzen 1700.
After several hours of mining with stable hashrates, pausing the CPU made the hashrates of both my RX 570 to drop and they didn't get back to their normal values until I restart the miner:

2 melloyellow

in my case srbminer works better with 290x. ~630h/s cn-heavy with clocks 1050/1375

JCE, are you planning on implementing parameterless config for your gpu miner?
If so would it be possible to do something like serviceconfig-v8.txt and serviceconfig-heavy.txt and have them called with something like this:

jce_cn_gpu_miner64.exe -c serviceconfig-v8.txt or jce_cn_gpu_miner64.exe -c serviceconfig-heavy.txt

------

Also could you re-confirm that you are getting these hashrates for a 290x

heavy @ 650+
{ "mode" : "GPU", "worksize" : 8, "alpha" : 256, "beta" : 8, "index" : ..., "multi_hash":448 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 256, "beta" : 8, "index" : ..., "multi_hash":448 },

v8 @ 850+
{ "mode" : "GPU", "worksize" : 8, "alpha" : 256, "beta" : 8, "index" : ..., "multi_hash":800 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 256, "beta" : 8, "index" : ..., "multi_hash":800 },

I'm not able to get near these speeds with those settings.  Granted the card I'm testing is a non reference 290x; I
think the reference cards behave better.  Could it be because I have used the example config in the download
and kept the other greek parameters in there?

Thanks

the hashrate drop is more imminent when you select only the 8gb cards. It won't even pickup the top hashrate. 
If I select both 4gb and 8gb cards together they would hit up the peak hashrates but would drop back later.

The problem is hard crash so the watchdog doesn´t help

Happy to heard that we are all behind you (at least the rx580 8gb owners)

My first tests on hybrid miner give interresting results on old cards. But not on new ones since the cost of sync tend to be higher than their native speed. But the main goal remains possible: put a big boost on older cards.


Isn't the Watchdog enough? Otherwise no problem to put just a message. GPU Stuck -> Watchdog enabled: Stop, disabled: Message.

a VERY BIG thank for this report, it probably confused lots of people. I'll re-upload the package with the comments fixed.

I could reproduce the drop problem on my RX on Heavy, at full speed my miner is clearly above others, but the drop is like -15% and this cancels any gain, as some stated. I've some ideas how to fix, need more time and tests.

Online is Linux CPU 0.33f
exact same as Windows version

thanks, that's it

Thanks for the clarification! I was still using them (transfered from some of the older configs). So the any numbers to play with are alpha and beta,  and other letters we can delete from the config?

Anyway, in 3 hours it will be about 24 hours since I switched my rigs from CN8 TR miner, to JCE heavy miner. 6 out of 7 Vega rigs are working without one single issue, except one rig that restarts every couple of hours, which brings me to following suggestion:

JCE,
please can you implement a warning message into the miner, when one card/thread stops hashing, to immediately write this message into log file? Now, if the card hangs the rig will crash before periodic hashrate reports. If there is one immediate warning message about the card, we can see it later in logfile and tune that card.
Thanks!

jesus no v8 for cpu 33f ?

Been using 33b6 since it came out and I can say there's nothing changed since b5. I can achieve stable hashrate but with much lower multihash. I'm talking about 570 4gb. I can get ~1000 out of those but only for a couple of minutes. Stable hashrate is around 800-900 (I used to get ~820 using 0.32q). So +20% boost is somewhat artificial for now. But on rx vega it does seem to be stable enough. I'm getting ~1840 per card for 24h+

Good! Cause there is some bug... Differenet launches this the same parameters can result different speeds...

that mix of Intel and autoconfig is clearly a bug, right i'll fix it. and it's pretty bad since it prevent the basic examples to start…

i'm still working on the warmup and stability problem on 8G+ cards.

I think, in starting of mining heavy algo 5 minutes warm-up needs to replace 15-20. I playing with different multi_hash parameters, but still no numbers that give stable speed... But warm-up period on heavy algo is much more than 5 min.

Please please please fix the warmup on RX470-480-570-580 8gb series... still having really bad speeds with b6. Only one out of 3-4 cards make it to full speed.

Thank you for the reply.

The missing gpu is a RX580.
GPU0 is intel HD and if I set --auto without using the -g option, it will try to mine with gpu 0,1,2,3,4 (that is intel graphics + 4 RX580) and gives a known opencl error because you can't mine on an intel HD graphics. GPU5 is listed but it doesn't start any thread for it. Using -c config.txt and specifying the 5 gpu's works as intended.
This is on a Asus z270-p with intel G4560 cpu and windows 10 ltsb (version 1607), jce_cn_gpu_miner.033b6
I have the intel graphics enabled so that the windows dwm.exe process doesn't allocate video memory on any rx580. Without it, I have to reduce intensity on the main gpu or the system lags and BSOD's

In short, the MoneroOcean mode is not supported yet in the GPU version. I'll add it, but not ready yet.

The CPU-only still exists because:
* It allows 32-bits mode
* It doesn't need OpenCL at startup (could be fixed in the GPU version)
* It has a linux version

-g is a restriction, so if a GPU is not enabled by the autoconfig, -g won't force it.
Is the missing GPU a Intel one? Intel GPU are detected but not enabled by default.

It's right I should clean some parts of the docs, but it's still better to keep two pages, because CPU and GPU config have each some exclusive features.

The GPU temperature/fan should work automatically, but if not, it's not blocking and it displays 0. I got reports about this bug but could never reproduce it