[JCE]Fast & stable CN/v8/Heavy/Tube/XHV miner, CPU+GPU, Vega56 1800+ RX580 1200+

[JCE-Miner]

Yes it works, i tested, but use --low on the cpu miner or it can annoy the gpu one. As a general rule, always use --low. it should have been the default value, but that's too late now i don't want to break interface.

to disable all cpu config and mining on the gpu version, parameter --no-cpu
the reciprocal --no-gpu exists too, but in such case, better stay on the pure cpu release.

[agismaniax]

can i use this miner with xmr-proxy?

https://imgur.com/a/Pb3Zps0
https://github.com/xmrig/xmrig-proxy

rem All is good ! Let's mine
@echo on
jce_cn_cpu_miner%BITS%.exe --auto --any --forever --nicehash --variation %FORK% --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %*
@pause

[syncro2017]

Yes it works, i tested, but use --low on the cpu miner or it can annoy the gpu one. As a general rule, always use --low. it should have been the default value, but that's too late now i don't want to break interface.

to disable all cpu config and mining on the gpu version, parameter --no-cpu
the reciprocal --no-gpu exists too, but in such case, better stay on the pure cpu release.

When do you plan to release the GPU version for testing?

[heet007]

I gave it a go to see how it compares with XMR-Stack on my dual mining rigs.  My results below are for CPU only. 

XMR:  500h/s (XMR-Stack) vs 330h/s (JCE)
  => ryzen 1800x
  => 34% decrease in hashrate

LOKI:  100h/s (XMR-Stack) vs 180h/s (JCE)
  => ryzen 1700x
  => 80% increase n hashrate

For both, the config file is the same.  Startup batch is different as i mining different coins using different algos on different pools. 

I am amazed how huge the hashrate variance is between the two coins.  But nevertheless very happy to see the hashrate of Loki go up so much. 
Is there any explanation for the variance between the two coins? 

I'll stick with XMR-Stack on Monero and see how JCE goes for a few days on Loki. 

[JCE-Miner]

JCE GPU to be released very soon. My code is done, i just need to polish some error messages and we go.

It will be an early protototype with very little doc and no autoconfig, but functional.

Performance : i thinks there's a difference in config in both case, there's no -34% or +80% perf difference on Ryzen, maybe 5-6%.
Be careful, the feature names are different, on JCE variation is the fork, while on xmrig it's the multi-hash, that XMRStak call low-power.

It may worth to look exactly at the chosen threads (number, cpu assignment, and multi-hash) on both and double-check it's the same.
However on old CPU like core2, JCE is really +35% faster.

Here's what I expect to be the best manual config on ryzen 1800x

Code:

"cpu_threads_conf" : 
[ 
     { "cpu_architecture" : "auto", "affine_to_cpu" : 0, "use_cache" : true, "multi_hash":1 },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 2, "use_cache" : true, "multi_hash":1 },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 4, "use_cache" : true, "multi_hash":1 },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 6, "use_cache" : true, "multi_hash":1 },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 8, "use_cache" : true, "multi_hash":1 },
     { "cpu_architecture" : "auto", "affine_to_cpu" :10, "use_cache" : true, "multi_hash":1 },
     { "cpu_architecture" : "auto", "affine_to_cpu" :12, "use_cache" : true, "multi_hash":1 },
     { "cpu_architecture" : "auto", "affine_to_cpu" :14, "use_cache" : true, "multi_hash":1 },
]

My stock R5 1600 gives ~498 h/s on XMR with JCE, and ~489 with stak, so your 330h/s looks strange, and even the 500 h/s of stak seems low.


JCE is not compatible with any proxy/socks, it must mine direct to pool. That's a security feature to avoid hackers embed the miner into a tunneled botnet. As I already said, I observed Claymore went this way, and I do the same.

edit
GPU prototype available
see first post

There's a little doc example in the github page. Only the manual config can enable the GPU for now. Autoconfig is still cpu-only.

[UnclWish]

Thanks for gpu update!
Tested new gpu part of miner...

What can I say... It's very good! Very!
Now my results. Tested on 270X 4Gb and RX 580 8Gb.

On all my cards best alpha is 64. 128 always lower speed, especcially on 270X.
Other greeks have too small affect...

CN-v7
270X - 528 h/s (m.hash - 464), Claymore 11.3 - 550 h/s and NO FEE (-h 460 -dmem 1)
RX580 - 970-975 h/s (m.hash - 1152), Claymore 11.3 - 967 h/s and NO FEE (-h 1152 -dmem 1), SRB miner 1.6.0 - 1025 h/s devfee 0.85% (intensity - 117)

CN-Heavy
270X - 412 h/s (m.hash - 448), Claymore 11.3 - no algo support, SRB miner 1.6.0 - 410-420 h/s devfee 0.85% (intensity - 27-28)
RX580 - 990 h/s (m.hash - 944), Claymore 11.3 - no algo support, SRB miner 1.6.1 - 1120 h/s devfee 0.85% (intensity - 59.5)

I didn't compare with XMRig and Stak because they are slower on my cards than Claymore or SRB. GGS is often between Claymore and SRB...

And another one thing: on RX 580 miner is stable. But on 270X 4Gb it often hangs computer till restart. Claymore 11.3 is very stable for it. So as SRB.

On Claymore and SRB it's more fine tuning of intensity. Your miner supports only multihash devided by 16. It's impossible to set multihash 460 for 270X, but it will be more speedy than 464, as I can see on Claymore.

All cards have modded bioses. And of course all tests was made on the same overclock and voltage settings. Drivers 18.6.1 Windows 10 x64 1803.

Good work! But it's still many improvements need to do.

P.S. Please make an option to disable detecttion of OpenCl devices so miner will be only CPU miner. OpenCL detection can affect on other miners if they allready running during your miner startup.

[JCE-Miner]

thanks for the feedback
your results are suprising on 270X on my hd7870 i really was far above Claymore, and Claymore is easy to configure.
against srb, well i probably didn't configure it at max but i couldn't reach the 540 i get on JCE. i'll retry with your exact same settings.

to disable opencl, parameter --no-gpu


also a very important thing, i let opencl allocate resource progressively, so the max hashrate is reached after a few minutes. at start, jce is often at 80% speed. Claymore punch the card to the max immediately. i'll add a message when the miner starts so people are not disapointed.

[Iamtutut]

Can you please ad this coin https://arqma.com/ ?
Algo is light v7

[JCE-Miner]

sure.
you can already mine it with --any --variation 4

to do now is multi-pool and gpu autoconfig

[Iamtutut]

Thanks a lot !

[nordmann666]

vega 56
     { "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 0, "multi_hash":1232 },
     { "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 0, "multi_hash":1232 },

~1800hs

but...would it not better to use seperate cpu miner with static difficulty? the GPU forced the pool to send high diff jobs = no shares found by CPU

[gvb]

JCE,

do I need to do anything special to have my GPU detected/enabled?

I have an AMD Radeon R7 200 I believe.

XMRig detects it but after a few jobs all counters remain 0 or N/A so I wanted to give your GPU version a try.

Edit: this shows XMRig for my card...

[2018-06-23 22:19:09] compiling code and initializing GPUs. This will take a while...
[2018-06-23 22:19:11] #0, GPU #0 AMD Radeon R7 200 Series, intensity: 576 (8/256), cu: 6

not a top class card but the extra 120H/s is better than nothing at all

[smparo]

JCE,

do I need to do anything special to have my GPU detected/enabled?

I have an AMD Radeon R7 200 I believe.

XMRig detects it but after a few jobs all counters remain 0 or N/A so I wanted to give your GPU version a try.

Edit: this shows XMRig for my card...

[2018-06-23 22:19:09] compiling code and initializing GPUs. This will take a while...
[2018-06-23 22:19:11] #0, GPU #0 AMD Radeon R7 200 Series, intensity: 576 (8/256), cu: 6

not a top class card but the extra 120H/s is better than nothing at all

You need to remove "--auto" in your start line and add "-c confgpu.txt", like this one
jce_cn_gpu_miner64.exe --any --forever --variation %FORK% --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %* -c confgpu.txt

Then edit the file confgpu.txt and change the parameters.
I have done some test with my R7 200 and i go to 140H/s with this parameter (memory at 1050MHz):

"gpu_threads_conf" :
[
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":400 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":400 },
]

[gvb]

wait a second... the link in the first post points to a download of the CPU only version

I'll download the right version first

[gvb]

ok, the right one is installed and it finds my main (shitty) intel gpu but not the secondary radeon R7.

might need to reboot due to that mining problem with XMRig, will do that after lunch and report here.

[UnclWish]

thanks for the feedback
your results are suprising on 270X on my hd7870 i really was far above Claymore, and Claymore is easy to configure.
against srb, well i probably didn't configure it at max but i couldn't reach the 540 i get on JCE. i'll retry with your exact same settings.

to disable opencl, parameter --no-gpu


also a very important thing, i let opencl allocate resource progressively, so the max hashrate is reached after a few minutes. at start, jce is often at 80% speed. Claymore punch the card to the max immediately. i'll add a message when the miner starts so people are not disapointed.

SRB miner latest versions works not so good on older cards like 2xx and 3xx.
I tried to wait some time and yes: speed grows. On 270X i got 545-546 h/s. But Claymore's 11.3 550 h/s still faster and without fee...
I think if you make multihash not devidable by 16 to make it possible to set it to 460, your miner can achive Claymore's speed...
Now will try heavy algo on 580...

P.S. You must add saving gpu kernels to not compile it every time like it SRB miner maked.

[gvb]

smparo,

from the moment that I add those GPU lines I get an invalid syntax error when I run the start batch file.

"cpu_threads_conf" :
[
     { "cpu_architecture" : "auto", "affine_to_cpu" : 0, "use_cache" : true, "multi_hash":1 },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 1, "use_cache" : true, "multi_hash":1 },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 2, "use_cache" : true, "multi_hash":1 },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 3, "use_cache" : true, "multi_hash":1 },
]

"gpu_threads_conf" :
[
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":400 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":400 },
]

It detects both my Interl (id:0) and AMD (id:1) now tho but it's not using any yet.

[smparo]

smparo,

from the moment that I add those GPU lines I get an invalid syntax error when I run the start batch file.

"cpu_threads_conf" :
[
     { "cpu_architecture" : "auto", "affine_to_cpu" : 0, "use_cache" : true, "multi_hash":1 },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 1, "use_cache" : true, "multi_hash":1 },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 2, "use_cache" : true, "multi_hash":1 },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 3, "use_cache" : true, "multi_hash":1 },
]

"gpu_threads_conf" :
[
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":400 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":400 },
]

It detects both my Interl (id:0) and AMD (id:1) now tho but it's not using any yet.

You made the same mistake I did 
Just add a comma before "gpu_threads_conf" :

],

"gpu_threads_conf" :
[

[UnclWish]

Heavy algo didn't grows up with time... At least about 10-15 min didn't added speed. So on RX 580 heavy algo max 1000 h/s. On SRB it's up to 1120 h/s.

[gvb]

You made the same mistake I did 
Just add a comma before "gpu_threads_conf" :
],
"gpu_threads_conf" :
[

Thanks that solved the syntax issue.

Now it seems to use 2 thread on the AMD and send some compiled code to it but the hash rate seems to stay on 0H/s.