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

[coke15]

hi jes'
i had faith when i see 33b 

[stsocrat]

Only "rejects" and "Invalid job id" regardless on pool and algo (v7/v8)
Hoped it works...
(vishera+5*baffin)

updated: works on cpu! had to install 18.6.1

[JCE-Miner]

Monero has just switched to v8
My miner works fine on v7, and on v8 CPU (but v8 GPU is broken, I know, i couldn't have finished it in time).
I'll redo some CPU tests on real Monero pools now it has switched.

regardless on pool and algo (v7/v8)

can you give an example of pool and algo you experienced a fail on? so I can test my side, at least on CPU

20:31:54 | CPU Thread 0 finds a Share, value 5000
20:31:54 | Accepted by the pool in 108 ms.

Tested right now by double-clicking the start.bat in the CPU package (which mine XMR v8 on the donation wallet)
So far, it just works.

note: since i cannot dev anymore on algos, being away of my rigs or any decent AMD gpu, i'm working on the algo autoswitch, Monero-Ocean style. It will be available on CPU version first.

[vmozara]

JCE,
I switched to srbminer until the gpu version is ready. Sorry man! 

[JCE-Miner]

Normal, i missed the deadline, so long. I still think I did the right thing by making the CPU version, JCE was already a CPU-only miner when v7 came out, turning into GPU-only would have been strange.

[wyzdic]

Normal, i missed the deadline, so long. I still think I did the right thing by making the CPU version, JCE was already a CPU-only miner when v7 came out, turning into GPU-only would have been strange.

wait your GPU version
your CPU version is good

[Lonnegan64]

Hi,

I'm using JCE especially on older systems without AES-NI, because this miner is without competition here. Perhaps some may want to know, what's up with cn/2 alias Cryptonight v8 here. The extra instructions seem to be hard work for the oldies. An AMD Opteron 1381 dropped from 70 H/s to 50 H/s, two Opteron 2374 HE (working with 6 Threads) dropped from 120 H/s to 70 H/s

Is there a chance for further optimizations or is all done what can be done with non-AES cpus?

[UnclWish]

It's strange... But, why if I manual set cpu_architecture to "vishera" (I have FX8320) then miner use assambly "generic_aes", but if I set cpu_architecture to "auto", then miner use assambly "generic_aes_avx"? I think with avx it's better?

[JCE-Miner]

There may be room for perf increase, even on non-AES. The 0.33a is already optimized, but not at max.

vishera

I'll take a look at my table of assemblies, I may have flagged Vishera to eas non-avx, which is safe, but wrong. If all vishera have AVX (i guess they have) so i'll fix. However the difference between aes and aes+avx is berely noticeable, except on the no-cache threads, where it gives a light boost (read: you go from 2h/s to 2.5h/s or something)

[stsocrat]

CPU version is working!
I have 8*8320E, 2*8320 and 6*8350. Now w/o oc.
On some Vishera auto uses only 5 cores, so i'm gonna -c config.txt with
"cpu_threads_conf" :
[
     { "cpu_architecture" : "auto", "affine_to_cpu" : 0, "use_cache" : true },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 1, "use_cache" : true },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 2, "use_cache" : true },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 3, "use_cache" : true },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 4, "use_cache" : true },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 5, "use_cache" : true },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 6, "use_cache" : true },
],

Adding
     { "cpu_architecture" : "auto", "affine_to_cpu" : 7, "use_cache" : true },
Slower

Adding
     { "cpu_architecture" : "auto", "affine_to_cpu" : 7, "use_cache" : false },
Plus 2h/s

Changing cpu6 into
     { "cpu_architecture" : "auto", "affine_to_cpu" : 6, "use_cache" : true,  "multi_hash": 2 },
Nothing interesting.

What's with v9?
Ok, nothing new.

[Nightworker88]

few weeks ago i switched to this awesome cpu miner.

Does anybody have a good and easier solution than eg. awesome miner for controlling the miners if they are alive?

I used to use for more than two years now claymore, and ethman was perfect to see on my desktop in my office whats going on with my rigs.

i was searching last days here in forum, but i did not find something, but i thinkthis is on one side myenglish and on other side i am an technician engineer and all this software is with less time little bit complicated for me

[JCE-Miner]

Hi all,

Still no way to fix openCL, but i've time to do some support here

HD7850 Radeon15.12Win7-64Bit

Win7 not supported, minimum is Win8.1, that's what I use for my Pitcairn rig.
But if you planned to mine Monero v8, it wouldn't have worked neither, my current v8 is broken on Pitcairn. other algo work fine, and CPU too.

a good and easier solution than eg. awesome miner for controlling the miners if they are alive?

My side, i provide a JSON server, that you can request to know if the miner is alive. Then some external tools can add a layer of abstraction over it. Try Forager, i know it supports JCE for a long time.

CPU version is working!

Nice to read

Vishera

I configure it by deafult as EAS but non-AVX, are all Vishera AVX-capable? I'll check and update my autoconfig.

Stuck at dev'ing only non-algo parts, i'm working on the MoneroOcean-style autoswitch on CPU version. Almost 60% done.

edit:

are all Vishera AVX-capable?

Yes they are. I fixed, and fixed also some other CPU where i did the same mistake. But don't expect a noticeable speed increase, except in no-cache mode.

[Bulitt]

Those dang Vishera CPU's have that unmanageable cache there are so many different configurations to try to extract the power from those CPU's and Ive always said there has to be a way to make a thread use a group of selected cores instead of just "false" and letting the OS manage the affinity.

Analyzing Processors topology...
AMD FX(tm)-8320 Eight-Core Processor
Assembly codename: generic_aes_avx
  SSE2          : Yes
  SSE3          : Yes
  SSE4          : Yes
  AES           : Yes
  AVX           : Yes
  AVX2          : No

Found CPU 0, with:
  L1 Cache:    16 KB
  L2 Cache:  2048 KB
  L3 Cache:  8192 KB, shared with CPU 1, 2, 3, 4, 5, 6, 7
Found CPU 1, with:
  L1 Cache:    16 KB
  L2 Cache:  2048 KB
  L3 Cache:  8192 KB, shared with CPU 0, 2, 3, 4, 5, 6, 7
Found CPU 2, with:
  L1 Cache:    16 KB
  L2 Cache:  2048 KB
  L3 Cache:  8192 KB, shared with CPU 0, 1, 3, 4, 5, 6, 7
Found CPU 3, with:
  L1 Cache:    16 KB
  L2 Cache:  2048 KB
  L3 Cache:  8192 KB, shared with CPU 0, 1, 2, 4, 5, 6, 7
Found CPU 4, with:
  L1 Cache:    16 KB
  L2 Cache:  2048 KB
  L3 Cache:  8192 KB, shared with CPU 0, 1, 2, 3, 5, 6, 7
Found CPU 5, with:
  L1 Cache:    16 KB
  L2 Cache:  2048 KB
  L3 Cache:  8192 KB, shared with CPU 0, 1, 2, 3, 4, 6, 7
Found CPU 6, with:
  L1 Cache:    16 KB
  L2 Cache:  2048 KB
  L3 Cache:  8192 KB, shared with CPU 0, 1, 2, 3, 4, 5, 7
Found CPU 7, with:
  L1 Cache:    16 KB
  L2 Cache:  2048 KB
  L3 Cache:  8192 KB, shared with CPU 0, 1, 2, 3, 4, 5, 6

I configure 4 standard threads to cores 7-5-3-1, then 2 "double cache" mode threads with affinity set to false. If only those 2 threads could be assigned to split their loads among cores 0-2-4-6 only I suspect theres an additional 60 or so more H/sec for a full CPU.

Code:

"cpu_threads_conf" : 
[ 
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 1, "use_cache" : true },
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 3, "use_cache" : true },
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 5, "use_cache" : true },
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 7, "use_cache" : true },
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 2, "use_cache" : true,},
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 4, "use_cache" : true,},
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 6, "use_cache" : true,}

]

00:18:48 | Hashrate CPU Thread 0: 61.29 h/s
00:18:48 | Hashrate CPU Thread 1: 46.64 h/s
00:18:48 | Hashrate CPU Thread 2: 46.53 h/s
00:18:48 | Hashrate CPU Thread 3: 45.79 h/s
00:18:48 | Hashrate CPU Thread 4: 46.69 h/s
00:18:48 | Hashrate CPU Thread 5: 46.61 h/s
00:18:48 | Hashrate CPU Thread 6: 46.31 h/s
00:18:48 | Total: 339.84 h/s - Max: 339.84 h/s

Code:

"cpu_threads_conf" : 
[ 
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 1, "use_cache" : true },
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 3, "use_cache" : true },
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 5, "use_cache" : true },
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 7, "use_cache" : true },
     { "cpu_architecture" : "vishera", "affine_to_cpu" : false, "use_cache" : true,},
     { "cpu_architecture" : "vishera", "affine_to_cpu" : false, "use_cache" : true,},

]

00:21:44 | Hashrate CPU Thread 0: 52.29 h/s
00:21:44 | Hashrate CPU Thread 1: 55.69 h/s
00:21:44 | Hashrate CPU Thread 2: 47.32 h/s
00:21:44 | Hashrate CPU Thread 3: 59.36 h/s
00:21:44 | Hashrate CPU Thread 4: 46.14 h/s
00:21:44 | Hashrate CPU Thread 5: 46.44 h/s
00:21:44 | Total: 307.22 h/s - Max: 307.22 h/s

Code:

"cpu_threads_conf" : 
[ 
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 1, "use_cache" : true },
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 3, "use_cache" : true },
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 5, "use_cache" : true },
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 7, "use_cache" : true },
     { "cpu_architecture" : "vishera", "affine_to_cpu" : false, "use_cache" : true, "multi_hash": 2 },
     { "cpu_architecture" : "vishera", "affine_to_cpu" : false, "use_cache" : true, "multi_hash": 2 }

]

00:24:22 | Hashrate CPU Thread 0: 47.41 h/s
00:24:22 | Hashrate CPU Thread 1: 55.00 h/s
00:24:22 | Hashrate CPU Thread 2: 42.57 h/s
00:24:22 | Hashrate CPU Thread 3: 58.28 h/s
00:24:22 | Hashrate CPU Thread 4: 47.22 h/s
00:24:22 | Hashrate CPU Thread 5: 46.72 h/s
00:24:22 | Total: 297.17 h/s - Max: 300.48 h/s

Code:

"cpu_threads_conf" : 
[ 
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 7, "use_cache" : true },
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 5, "use_cache" : true },
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 3, "use_cache" : true },
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 1, "use_cache" : true },
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 0, "use_cache" : true },
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 2, "use_cache" : true },

]

00:27:53 | Hashrate CPU Thread 0: 61.01 h/s
00:27:53 | Hashrate CPU Thread 1: 61.36 h/s
00:27:53 | Hashrate CPU Thread 2: 46.30 h/s
00:27:53 | Hashrate CPU Thread 3: 47.12 h/s
00:27:53 | Hashrate CPU Thread 4: 46.66 h/s
00:27:53 | Hashrate CPU Thread 5: 46.29 h/s
00:27:53 | Total: 308.72 h/s - Max: 309.41 h/s

And this is the way you're "supposed" to do it based on the L3 cache amount

Code:

"cpu_threads_conf" : 
[ 
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 7, "use_cache" : true },
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 5, "use_cache" : true },
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 3, "use_cache" : true },
     { "cpu_architecture" : "vishera", "affine_to_cpu" : 1, "use_cache" : true },

]

00:29:52 | Hashrate CPU Thread 0: 61.28 h/s
00:29:52 | Hashrate CPU Thread 1: 61.34 h/s
00:29:52 | Hashrate CPU Thread 2: 61.49 h/s
00:29:52 | Hashrate CPU Thread 3: 61.62 h/s
00:29:52 | Total: 245.71 h/s - Max: 245.71 h/s

[kosmoo]

нe paбoтaeт нa win7. He oпpeдeляeт GPU. Жaль. Удaляю

[UnclWish]

нe paбoтaeт нa win7. He oпpeдeляeт GPU. Жaль. Удaляю

100 paз былo cкaзaнo, чтo мaйнep GPU нe paбoтaeт нa Windows 7. Пoд 7-кy yжe дpoвa cкopo пepecтaнyт пиcaть нoвыe, зaчeм нa нeй cидeть...

[Lonnegan64]

It's interesting, that cn/2 alias Monero v8 has different impact on different CPUs. With Zen it's relatively moderate, AMD Ryzen 7 2700 dropped from 620 H/s to 595 H/s (-4%).

On Bulldozer-based CPUs instead, it's devastating! A8-5600K "Piledriver" dropped from 155 H/s to 119 H/s (-24%), Opteron 4284 "Zambezi" from 280 H/s to 180 H/s (-35%) and A8-7600 "Kaveri" clashed from 177 H/s to 94 H/s  (-47%).

Apparently this are the archs, which were not cache limited, but are limited in execution units, pipelines and/or instructions on the fly, whereas a CPU like Ryzen is wide enough to do the extra instructions on the side. 

[JCE-Miner]

The old Core2 suffer also from the new algo...

I'm done with the Algo-autoselect switch version for CPU. I write here a preview of the features. The final doc will be on the Github page.
I need to test more, but the code itself is done. I'll test on MoneroOcean, betting other pools are compatible

Config
Autoswitch is --variation 16
If you mine with --auto, that's it.
Otherwise, the manual config is a lot more complicated: there are three new arrays:

Code:

"cryptolight_cpu_threads_conf"
"cryptonight_cpu_threads_conf"
"cn_heavy_cpu_threads_conf"

Respectively for the
Cryptolight algo family (Turtle, Red...)
Cryptonight algo family (Monero, Stellite, Masari...)
Heavy family (Loki, Haven, Tube...)

Each array is filled the same way as the legacy "cpu_threads_conf", but is algo family specialized. They don't overlap, "cpu_threads_conf" is used for and only for the normal single-algo mining, and the three other for and only for the Autoswitch.
Not the three are mandatory, only one is, an indirect way to disable algo families you don't want to mine. For example, not to mine heavy-class algos, just don't set any "cn_heavy_cpu_threads_conf" in your config. MoneroOcean, however, requires at least the Cryptonight family to be enabled.
I advise, for readability, to use separate config files for single-algo and Autoswitch, but the same file can hold the four arrays, no problem.

Preview

Code:

"cryptonight_cpu_threads_conf" : 
[ 
      { "cpu_architecture" : "core2_sse4", "affine_to_cpu" : 0, "use_cache" : true, "multi_hash":1 },
      { "cpu_architecture" : "core2_sse4", "affine_to_cpu" : 1, "use_cache" : true, "multi_hash":1 },
],

"cryptolight_cpu_threads_conf" : 
[ 
      { "cpu_architecture" : "core2_sse4", "affine_to_cpu" : 1, "use_cache" : true, "multi_hash":1 },
],

Code:

+-- Thread 0 config ------------------------+
| Dedicated to:          Cryptolight/forks  |
| Run on CPU:            1                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       core2_sse4         |
+-------------------------------------------+

+-- Thread 1 config ------------------------+
| Dedicated to:          Cryptonight/forks  |
| Run on CPU:            0                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       core2_sse4         |
+-------------------------------------------+

+-- Thread 2 config ------------------------+
| Dedicated to:          Cryptonight/forks  |
| Run on CPU:            1                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       core2_sse4         |
+-------------------------------------------+

Dedicated: for the threads that starts or stops depending on the algo family. Here, either thread 0 or 1+2 will mine, but not all.

Code:

22:08:37 | Connected to pool. Now logging in...
22:08:37 | Algo-autoswitch Pool gets proposed:
22:08:37 | * Original Cryptonight
22:08:37 | * Original Cryptolight
22:08:37 | * Cryptonight V7 fork of April-2018
22:08:37 | * Cryptolight V7 fork of April-2018
22:08:37 | * Cryptonight-XTL fork of May-2018
22:08:37 | * Cryptonight-Alloy fork of May-2018
22:08:37 | * Cryptonight-MKT/B2N fork of May-2018
22:08:37 | * Cryptonight-Arto fork of May-2018
22:08:37 | * Cryptonight-Fast MSR fork of June-2018
22:08:37 | * Cryptolight-Red fork of July-2018
22:08:37 | * Cryptonight V8 fork of Oct-2018
22:08:38 | Successfuly logged as .......
22:08:38 | Auto-select algo switched to: Cryptonight V8 fork of Oct-2018
22:08:38 | Pool changes Difficulty to 100.
22:08:38 | CPU Thread 2 for Cryptonight/forks wakes-up.
22:08:38 | CPU Thread 1 for Cryptonight/forks wakes-up.
22:08:43 | Hashrate CPU Thread 1: 0.00 h/s
22:08:43 | Hashrate CPU Thread 2: 0.00 h/s
22:08:43 | Total: 0.00 h/s - Max: 0.00 h/s

The startup is a lot more verbose.
First, JCE lists the algo proposed to the Pool. Of course some may be ignored by this latter, i doubt MoneroOcean will make me mine CN-Red, but that's harmless. Since I configured Cryptonight and Cryptolight, but not Heavy, the Heavy-class are not listed.

The after the login, the Algo chosen by the pool is displayed. It will be displayed each time it changes.
When the algo family changes (to switch from Monero to Turtle for example) the respective threads stop and start.
Only active threads count for the hashrate, the other are ignored.

Here I simulated with my netcode a switch to CN-Light v0 (wich would hardly happen in real life, that's for example):

Code:

22:09:00 | CPU Thread 2 finds a Share, value 100
22:09:00 | Accepted by the pool in 121 ms.
22:09:03 | Pool changes Difficulty to 469.
22:09:24 | CPU Thread 2 finds a Share, value 469
22:09:24 | Accepted by the pool in 126 ms.
22:10:03 | Auto-select algo switched to: Original Cryptolight
22:10:03 | Pool changes Difficulty to 304.
22:10:03 | CPU Thread 1 for Cryptonight/forks suspends.
22:10:03 | CPU Thread 2 for Cryptonight/forks suspends.
22:10:03 | CPU Thread 0 for Cryptolight/forks wakes-up.
22:10:15 | CPU Thread 0 Lane 0 finds a Share, value 304
....

Fees
No change, fees are mined in the same algo than the user. In case of autoswitch, that will be the current algo when the fee sessions starts.

Compatibility
100% backward compatible with previous JCE. About the pool, i'm testing on MoneroOcean.

Release planned for Windows CPU in a few days, when my tests are done. Then Linux CPU. No GPU version until november, for the exact same reasons I cannot provide a working GPU v8

[sergneo]

Test autoselect also on Minergate pool, please 

[JCE-Miner]

Stupid question: is Minergate an algo-switching pool, in the same sens as MoneroOcean ?
If yes, i didn't find how.
The doc:

https://minergate.com/altminers/claymore-cpu

provides a different address for each coin, like a normal pool.

[almost30]

hi dev , thanks for your hard work .
last update i mange to run 4 vega cards with no problem  . (-G 0,1,2,3)
but the miner stuck if i add 5th card (-G 0,1,2,3,4) .


any reason why is this happens !