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

[dnkn]

Same as mentioned but multi_hash 992 gave me 1840-1890 on vega56 but... I had to stop mining heavy with this miner for now as the hashrate is not stable at all. It can be 16** or 18** or even 15**. I tried tons of settings, it looks to be random. The same goes for rx5** series. Sometimes I have 650hs sometimes 1020. From the very same gpu with the very same freqs/voltages. Rx560 4gb perform much better in previous versions , they deliver stable 590-600hs, and only 460 with this version.

[1714243460]

1714243460

[1714243460]

1714243460

[1714243460]

1714243460

[1714243460]

1714243460

[1714243460]

1714243460

[dragonmike]

I'm experimenting a very different implementation, JCE Hybrid Miner, with the AES job done by the CPU in a split second (because an AES CPU is basically an AES one-cycle asic) and only the scratchpad done by the GPU, with the requirement the CPU is aes-compatible, and the GPU memory relocated is above 4G (option in most BIOSes).
If it works, performance should skyrockets The bottleneck is the synchronization, which is fine on OpenCL for FPGA (like Intel or Xilix) but not on AMD GPUs.

Let me know if you need any independent beta-testing

You (or someone else with proper skills) need to bake a proper x16r miner for AMD. Anything so far has been grossly underwhelming.

[Lermite]

You (or someone else with proper skills) need to bake a proper x16r miner for AMD. Anything so far has been grossly underwhelming.

Did you try Wildrig on X16R?
https://bitcointalk.org/index.php?topic=5023676.0

I've just begun testing it and I don't know yet if it's worth.

[dragonmike]

You (or someone else with proper skills) need to bake a proper x16r miner for AMD. Anything so far has been grossly underwhelming.

Did you try Wildrig on X16R?
https://bitcointalk.org/index.php?topic=5023676.0

I've just begun testing it and I don't know yet if it's worth.

Yes I have.
No it's not better.

Just another "optimisation" of a stone-age SGminer kernel from Wolf0.

[1033ruben]

yes hello to all i would really like to try this miner out but i just cant/dont understand how to Start it up. I know with xmr stak and srb i would just run the application and then i would fill in the blanks. and then i could edit/ tweak from there i have 4 mining rigs 2 nvidia and 2 amd. i am currently running cryptonight on both of my amd and also on my 2 nvidia rigs cpus. any help would be great it is for a 6800k, ryzen5 1600 and an 8700k. my last irg is a lowly g4400. again any help would be greatly appreciated on how to get this miner up and running.
THANKS IN ADVANCE!!!

[Nightworker88]

1033ruben

exactly with JCE miner it is complitly simple:

open the miner folder - find "start", click right mouse on it .edit.

then just change:

1. pool address
2. port number
3. ssl or no ssl
4. wallet adress.payment id
5.chosse algo : in the end of the list write number
6. last line is the .bat ( if you want change some paramaters, please read the help, does mean start the help.bat

so, for example my simple bat:


jce_cn_gpu_miner64.exe --no-cpu -g 1,2,3,4 --bus-order --doublecheck --watchdog 10 --retrydelay 10 --keepalive --auto --any --forever --variation %FORK% --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %*

 

[QuirkSilver]

Hi, why the hash rate fluctuations? haven heavy or v8 on 4gb.... most fluctuate much..... on 2x 570 and one 560, the hash rate fluctuates on them as if its linked..... Multi hash not really much influential, however that 0.33b5 is Really fast..... samsung 8gb rx 470, haven, 1130 h/s etc. But some other GPUs are very low rate although they have good timings multi hash 944x2 , 8 work size on heavy 8 gb works but some doesnt like it..... dropping to 960+896 or even 896X2 doesn't fix much

I have up to date windows, fresh reset, 18.6.1 drivers..... more than enough virtual memory but only 4gb of ram. windows up to date. slots are 1.1 pcie tried going 2.0 yesterday , didnt notice much difference.

last i used was one of thos 0.31 copies that were slow in mining start, used to steadliy on hynix 8gb give 1090 h/s with 944 multi hash X2

[UnclWish]

With the last version 0.33b5 i'm not that sure the best multi_hash is the max any longer. To be tested, but on my two RX560 one 2G one 4G, the 4G is no longer the fastest. And high values tend to make the hashrate less stable on RX.

I tried to lower multi_hash for heavy algo. It makes speed more stable, but it became slower.

[io8621]

Tested jce with different gpu. On old gpu like 370 works fine, on v8 can get more than 500 hs. On rx series 4 gb working good.
But i have a lot of problem with 8gb card.
Example, sapphire pulse rx580 8gb hynix memory, fresh windows install with 18.6.1 driver.
Tested with multiple bios mod, srebpolaris 3.5, pbe 3 or 1.6.7 i get very unstable hashrate max to 940 hs, this with 033b4.
With 033b5 can get > than 1000 hs but very very unstable hashrate.
On srbminer get 950 hs but stable without fluctuation.

1200 gpu 2100 or 2150 mem without memory error.

Other experiences with this gpu? Can you get stable 1000 hs or more on v8?

[fluxy12]

Hello,

I've done all test possible with one of my rx580 rigs (6 cards) - OC, multihash, multi windows, ... - the last version is not stable, it is impossible to get all 6 cards to max hashrate.

I've come back to older versions waiting for a stable version.

[io8621]

Thank you for the confirmation. With previous versions, 033b4 in particular, how much can you get?

[JCE-Miner]

i read your reports about hashrate stability, i'll focus on stabilize Heavy hashrate as the top priority

[Axadiw]

It first i’ve posted this on https://github.com/jceminer/cn_cpu_miner/issues/26 but here I might get the anser quicker:

Code:

is it possible somehow to specify which algorithms should be selected when using "Pool-managed Autoswitch" variany in JCE?

I have been previously mining on MoneroOcean with MM.js proxy miner, that've configured with manually gathered performance benchmarks, for example:

...
"algo_perf": {
     "cn/xtl": 54.17,
     "cn/2": 54.56,
     "cn/msr": 111.15,
     "cn-lite": 172.73,
     "cn-heavy": 29.44,
     "cn-heavy/tube": 22.53
    },
With these, MoneroOcean is able to decide which coin would be most profitable to mine on my setup (in my case, it would be cn-lite algorithm, a.k.a Cryptolight V7 fork of April-2018)

Unfortunately when I've configured JCE miner with variant 16 (Pool-managed Autoswitch) - it's mining only with Cryptonight V8 fork of Oct-2018.

Is it possible to specify somehow particular algorithms performance, that would be than used by MoneroOcean to decide which coin is most profitable to mine?

[bucah]

guys! i recently got a rx550, 2gb. Any idea if i can get more than 300h/s on cn-heavy?

14:52:33 | Hashrate CPU Thread 0: 30.92 h/s - Total CPUs: 30.92 h/s
14:52:33 | Hashrate GPU Thread 1: 168.05 h/s
14:52:33 | Hashrate GPU Thread 2: 168.01 h/s - Total GPU 0: 336.05 h/s
14:52:33 | Hashrate GPU Thread 3: 853.76 h/s
14:52:33 | Hashrate GPU Thread 4: 854.35 h/s - Total GPU 1: 1708.10 h/s
14:52:33 | Hashrate GPU Thread 5: 863.24 h/s
14:52:33 | Hashrate GPU Thread 6: 867.02 h/s - Total GPU 2: 1730.25 h/s
14:52:33 | Hashrate GPU Thread 7: 828.42 h/s
14:52:33 | Hashrate GPU Thread 8: 829.00 h/s - Total GPU 3: 1657.42 h/s
14:52:33 | Hashrate GPU Thread 9: 850.04 h/s
14:52:33 | Hashrate GPU Thread 10: 851.09 h/s - Total GPU 4: 1701.12 h/s
14:52:33 | Total: 7163.84 h/s - Max: 7164.03 h/s

GPU 0 is Gigabyte RX550 2GB (elpida) mining on Haven and as a display
Here is my config :
 
   { "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash":216 },
   { "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash":216 },
   

However, there is one strange thing about my Vega 56 hashrate. 1 of any Vega (random) always drop to 16xx h/s (about 60 h/s) after each miner restart.
Here are my Vega 56 config :

   { "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash":896 },
   { "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash":896 },
   { "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 3, "multi_hash":896 },
   { "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 3, "multi_hash":896 },
   { "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 4, "multi_hash":896 },
   { "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 4, "multi_hash":896 },
   { "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 5, "multi_hash":896 },
   { "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 5, "multi_hash":896 },

Any ideas ??

PPT according to vegaminingguides.com but Core @870mV and memory @860mV

[Mashy81]

Hashrate is unstable. I just restarted a few times until I got stable hashrate.
Now getting 1800hs on vega56 stable. 1470/899mv core  1098/870mv memory
Whole rig.
2x rx570 4gb and 4x vega56
8970hs  940watts at the wall.
Just waiting to confirm on the long run at pool hashrate.

[Aerocool]

i read your reports about hashrate stability, i'll focus on stabilize Heavy hashrate as the top priority

Hi. Miner not work with format "user wallet + paymentID.diff". Can you fix it? Please)

[Iamtutut]

0.33 B5 is ways too unstable on my system, even after lowering the intensity.

0.33 B4 seems to work better.

My 3 GPU are RX570 4GB with undervolting and mem OC. I have a very stable and satisfying config with 0.32G.

Right now mining XTL.

HR: 2739H/s, power: 335W

Code:

"gpu_threads_conf" : 
[ 
	{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash": 672},
	{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash": 672},
	{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash": 928},
	{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash": 928},
	{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash": 912},
	{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash": 912},
],

[dragonmike]

0.33 B5 is ways too unstable on my system, even after lowering the intensity.

0.33 B4 seems to work better.

My 3 GPU are RX570 4GB with undervolting and mem OC. I have a very stable and satisfying config with 0.32G.

Right now mining XTL.

HR: 2739H/s, power: 335W

Code:

"gpu_threads_conf" : 
[ 
	{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash": 672},
	{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash": 672},
	{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash": 928},
	{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash": 928},
	{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash": 912},
	{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash": 912},
],

Have you tried lower intensities?
I found 464 (and 448 for one card) to be the best. Anything above that and it'll start crashing. Hashrate per 570 is 857 h/s across all 7 cards of my rig (some are flaky so clocked a bit lower - range is basically 825-900).

[Dmialdav]

Hello!
After updating 0.33h and higher, an error appears when starting the miner:

Abort was called at 318 line in file:
D:\qb\workspace\19992\src\vpg-compute-neo\runtime\os_interface\windows\wddm.cpp

Help fix it. 6*Vega64, Win10, 18.6.1 drivers.

[JCE-Miner]

hello!

Documentation:
https://github.com/jceminer/cn_gpu_miner#troubleshooting

Last question:

Q. I get error D:\qb\workspace\19992\src\vpg-compute-neo\runtime\os_interface\windows\wddm.cpp
Intel GPUs are now enabled among AMD GPUs, ensure you're not applying a previous AMD configuration to an Intel GPU

I'm about to release a minor update with more stable hashrates for Heavy (I hope...), no more autoconfig on Intel GPU (causes a lot of troubles) and smoother autoconfig on AMD ones. And a little optim for Monero v8.