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

[BS0D]

JSON: is it really forbidden by the json standard to write

Code:

"a" : 
{42}

rather than

Code:

"a" :{
42}

?

It may be acceptable by json standard but any json validator fixes the code that way.
May be the problem occurs when using 'json.parse' where every single string should be understood as it should be. For example the string starting with "hashrate": should end with a value or a bracket.
I maybe wrong ofcourse.

[JCE-Miner]

http://json.org/

ws
    ""
    '0009' ws
    '000a' ws
    '000d' ws
    '0020' ws

Whitespace can be inserted between any pair of tokens.

So my JSON is conformant, and said differently, JSON do'nt care about blankspaces and indentation.

0.33b6 to be released in less than one day, with the OpenCL bug O.2.10 fixed.

[lebuawu2]

My Vega56 rig is doing much better than it was on SRB. I had to adapt some of the settings I was using on SRB to JCE to get the most hash (per GPU, 1 thread with 1008 multi_hash and 1 thread with 880 multi_hash)

My RX580 8GBs are par for the course compared to SRB no matter what I tried but I'm still using JCE because I like the effective hash stat

Interesting config, is it better than both thread with multi_hash 944?

[JCE-Miner]

I won't comment about the speed, happy if you got it better, but about the settings: Cast, SRB, TeamRed and JCE are close source miners, with different code each. We obviously don't use the reference code (the one of XMRig/stak). So we have each our own best settings, and we don't even use the same units, SRB intensity setting (a number somewhere between 0 and ~100) is unlike my multi_hash which is often arount 500, 1000 or 2000, alpha and beta. For each miner, take time to tune, even between two revisions of same miner.

On GitHub I often get tickets from people who complain they cannot apply one-to-one their xmrstak config. I don't know how and where to say we're two unrelated software 

0.33b6 done, now testing. Planned fixes:

OpenCL O-2.10 bug solved
More stable hashrate
Little perf boost on all algos ~0.15%
Temperature Watchdog (AMD GPUs only)

[dnkn]

Dunno if it's of any help to fix unstable hashrate but I settled on this config for rx570 4gb (880-910 per card).

{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":448 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":448 },

And the same but multihash 992 gives me 1830-1870 from vega56. 11.1kh from 6 gpu rig. 1014watts. That rig has been working for 24 hours and hashrate drop was insignificant (10.9kh). But the other rx vega rig works best with multihash 960. I may be wrong but looks like both threads have to have equal multihash and that was not the case in the previous versions.

Big thanks for this great miner!

[BS0D]

[JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s

I've got 1800h/s with cn-tube on V64. Very good result.

[vmozara]

[JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s

I've got 1800h/s with cn-tube on V64. Very good result.

Please can you share your setup?

I easily got 1800 on single vega pc but on my rigs hashrates are anywhere from 1500 to 1800. Hoping that b6 version will resolve that and provide consistent hashrate

[BS0D]

[JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s

I've got 1800h/s with cn-tube on V64. Very good result.

Please can you share your setup?

I easily got 1800 on single vega pc but on my rigs hashrates are anywhere from 1500 to 1800. Hoping that b6 version will resolve that and provide consistent hashrate

I use that, but got one vega:
"gpu_threads_conf" :
[
{"index": 0, "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 32, "multi_hash": 960},
{"index": 0, "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 16, "multi_hash": 1008}
]

This conf seems very close to max available memory usage and after miner restart it cannot allocate memory for one of threads. IDK if that is about vega memory or swapfile. It somehow keeps some data after use. SRB solves the same like issue when restarting vega and releasing memory if I'm right.

[varusisog]

I have a few R9 390/390X. What is the optimum configuration?

[UnclWish]

I don't think that on HD6990 or 390 mining is profitable at this moment... Power costs more than these cards can mine...

[JCE-Miner]

I'm claiming to be the fastest on old GPU and I don't even provide a decent autoconfig for old cards, what a shame...
I'll update some autoconf for those cards like Cayman, Tahiti, Bonaire or Pitcairn.

Perf on HD6990:
https://github.com/jceminer/cn_gpu_miner/issues/26

This guy shared his config that goes to 270 h/s per GPU (HD6990 is a dual GPU) with no memory strip hack (which is lame, i will advise him to patch his BIOS).

Settings used : 32 worksize and 864 intensity.

I guess that's on one thread per GPU, the dual threading is for GCN cards.
It translates:

Code:

{ "mode" : "GPU", "worksize" : 32, "alpha" : 64, "beta" : 8, "index" : ...., "multi_hash":864 } 

Thanks all for report and sharing your optimal config. Don't forget to tell what algo you're mining
so i can put those config in the Github doc.

Tuning is just a bit of a hobby of mine

I usualy get complains about the parameters being too numerous (there are four). Not to few.
Greeks above beta are deprecated, worksize is very like in XMRstak, multi_hash is like XMRstak intensity (but unlike SRB intensity) and alpha/beta are internal data packing parameters, no general rule, sometimes doing x2 or /2 on the defaults gives a little boost. Depends on the card and algo you mine. My autoconfig always defaults to 64 and 8.

[JCE-Miner]

I don't think that on HD6990 or 390 mining is profitable at this moment... Power costs more than these cards can mine...

If my hybrid miner works, it may resurect the old card mining, like I resurected Core2 and Opteron mining with JCE CPU on V7. I admit they lost a lot of efficiency on v8.

[dnkn]

Unfortunately it has happened again. Hashrate drop. Cruel hashrate drop. From 26-27kh to 20.5-22. This was at the first day I tried 0.33b5 but then I tried different settings and everything seemed fine until several hours ago. I noticed that my hashrate on pool decreased and I noticed that effective hashrate reported by jce has decreased too. I tried to restart miner/reboot rigs, nothing helps. I'll wait for the next version. I'm sure it'll be fixed.

[1033ruben]

Will any one be so kind as to share their config file for CNV7 for a ryzen 5 1600 cpu.
THANKS IN ADVANCE

[JCE-Miner]

It's online 0.33b6 GPU

I mined Haven for 48 hours on 3 capricious RX and had a very stable hashrate, varying +/- 2% not more, I hope it will be better for everybody.

Code:

Fixed the OpenCL bug 0-2.10
Stabilized hashrate
Updated doc
Updated autoconfig for older cards
Little perf boost
Temperature watchdog (default: disabled)

Will any one be so kind as to share their config file for CNV7 for a ryzen 5 1600 cpu.
THANKS IN ADVANCE

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" : 11, "use_cache" : true, "multi_hash":1 },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 1, "use_cache" : true, "multi_hash":1 },
],

[salamor]

V0.33.B4:
rx 564 - ~580 h
rx 584 - ~760 h
rx 588 - ~1030 h
 нecтaбильный зaпycк, мaкc xeш co 2-4 пoпытки

V0.33b5:
rx 564 - ~450 h
rx 584 - ~930 h
rx 588 - ~900 h
нecтaбильный зaпycк, мaкc xeш co 2-4 пoпытки

i3 - 8350k вceгдa - ~143h

измeнeниe config нe пoмoгaeт

[Iamtutut]

It's online 0.33b6 GPU

I mined Haven for 48 hours on 3 capricious RX and had a very stable hashrate, varying +/- 2% not more, I hope it will be better for everybody.

My GPUs could get through the warmup, still with swings (mostly RAM frequency, sometimes core freq). Declared speed in itself is highly improved compared to my reference JCE 0.32G version, +15% for same power draw (at wall). If my computer stay stable during the night, I'll check the reported HR at the pool.

[vmozara]

b6 version:
vega rig i think all 7 cards are 56@64, platinum PSU
custom 880 ppt, 1450/1100 forgot the driver version, multihash 896

total hashrate 12120 pulling 1120W from the wall. This are great figures that put heavy algos highly on the profitability list. This is my first epxerience with heavy algos, i don´t know any coins (mining bit tube now for testing) but if this proves good and stable for my vega machines, i will probably switch all rigs to reduce the temperatures and strain on my rigs.

not sure if I want to leave it running overnight, as i have no access to internet once i leave the workshop.

Please share your full setup when writing about hashrates

JCE thanks for awesome miner, please keep developing, you think you can squeeze more hash out from heavy?

[vmozara]

My GPUs could get through the warmup, still with swings (mostly RAM frequency, sometimes core freq). Declared speed in itself is highly improved compared to my reference JCE 0.32G version, +15% for same power draw (at wall). If my computer stay stable during the night, I'll check the reported HR at the pool.

We don´t have same cards, but I did 3 things at same time that equalized and stabilized hashrate over my rigs:
1; Changed multihash from 960 to 896 (vega cards)
2. Changed miner to low priority ( --low). My CPU is very slow (celeron 3855U) and probaby has issues when any load is applied to it
3. Updated from b5 to b6

try fiddling with any of these settings, maybe it gets stable

[BS0D]

The last point I've reached is quite stable heavy 1920-1930h/s, single Vega 64 (1478/920 1100/910). But still I don't understand what it depends on.
{ "mode" : "GPU", "worksize" : 8, "alpha" : 68, "beta" : 64, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":960 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 68, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":1008 }
About 80-100h/s appears when playing with alpha 64-68 on threads.
It can start with rising to 1950-1970 but then it falls to 1830-1840 (which is very good too). But it can also start with straight 1920 and work with stable 1920-1930h/s with no issues.
And that's with usage of FX4330(4-core, 8M, 4GHz) in that same config:
{ "cpu_architecture": "auto", "affine_to_cpu": 0, "use_cache": true, "multi_hash": 1 },
{ "cpu_architecture": "auto", "affine_to_cpu": 3, "use_cache": true, "multi_hash": 2 }
which does 120h/s.
I think it's all about some megabytes of memory usage.