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

[vmozara]

I don´t know, it is either 18.6.1 or 18.7.1, i didn´t try newest driver. 2000 worked on vegas 56 but didn´t work on vegas 64 when i tried, they were hashing 0. I will be back home in 10 days (i am onboard the ship) then i need to standardize my miners, drivers and settings. now it is all over the place, my rigs have miners from JCE from 31a all the way to 32g, so can´t really give any reliable information now

[EMWEE]

Tried your miner on a old G7 server with 4 Nehalem Xeon's (no AES) and my hashrate increased from 600 with xmrig to 725 with jce.

[whotheff]

Any CUDA support in near future?

[Uaciuganadu]

Hello,

i plan to add per-gpu coin config, to allow different gpu mine different coins, since some are faster on Heavy or on V7. but not a super autoswitch, that goes too far for now.

Thank you for the info. It seems like most miners will adopt the auto switching stuff after the figure out a good way to take the DevFee and not restart the miner every time a more profitable coin is found.

doktor83 is planing to add this in the next version of SRB Minerto support mining on MoneroOcean and other new pools that may go this route because there are so many fluctuations and speculations on the market.

I hope we will have this in JCE Miner in the near future as well. I really like how you develop things and I truly think you can find a way to make it switch algo on the fly based on some bench-marked saved presets.

[JCE-Miner]

Hello all!

Xeon : yeah JCE is by far the fastest on old CPU, that's my niche expertise, but i expect +30% compared to other miners, maybe you should try to fine-tune a bit with the manual config, if not already done such.

fan/speed zero: i got some report about this but I cannot work on it as top priority, for now that number is rather cosmetical.

warmup : i need to improve it a bit to make the 8- or 12- gpu rigs work well.

cuda: unlikely, i've so many things to fix just on the AMD version... at least i should make my code compatible with nvidia's OpenCL (and Intel one too).

Next planned versions:
- Minor 0.32h : zBucks and XCash new coins, improved GPU report (will add shares found/accepted/reject and overall hashrate per gpu)
- Major 0.32i : watchdog

and some warmup fixes on the fly. probably no perf changes.

[heavyarms1912]

0.32g is less stable for me.  I had 1 GPU that stopped mining on two separate rigs in a day of mining.  0.32e worked for days.  Did anything change for CN-V7 between these version @JCE-Miner.

Also is it possible to have bus_id initialization of gpus?

[vmozara]

JCE is any update coming to next few days? I was thinking to standardize all my rigs instead of having big mess of miner versions and drivers.

Also,
it would be cool if you put one simple info to new versions: if they are compatible with old versions of config and start files. If yes, then we can simply extract into existing folder excluding old config and start and have the miner ready in seconds. Nothing for you to do, just when new version is ready, inform if there are any issue with old files.

[lmnop]

On dual socket xeon can JCE use cpu numbers over 16? Im trying to get 20 threads running with 40MB L3 over 2 sockets.

I get this error

Invalid configuration for CPU thread 10: value in 'affine_to_cpu' (64) must be less than your number of CPU (16).
Press any key to continue . . .


with the following --probe

Analyzing Processors topology...
Dual Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
Assembly codename: generic_aes_avx
  SSE2          : Yes
  SSE3          : Yes
  SSE4          : Yes
  AES           : Yes
  AVX           : Yes
  AVX2          : Yes

Found CPU 0, with:
  L1 Cache:    32 KB, shared with CPU 1
  L2 Cache:   256 KB, shared with CPU 1
  L3 Cache: 20480 KB, shared with CPU 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13,
 14, 15
Found CPU 1, with:
  L1 Cache:    32 KB, shared with CPU 0
  L2 Cache:   256 KB, shared with CPU 0
  L3 Cache: 20480 KB, shared with CPU 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13,
 14, 15
Found CPU 2, with:
  L1 Cache:    32 KB, shared with CPU 3
  L2 Cache:   256 KB, shared with CPU 3
  L3 Cache: 20480 KB, shared with CPU 0, 1, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13,
 14, 15
Found CPU 3, with:
  L1 Cache:    32 KB, shared with CPU 2
  L2 Cache:   256 KB, shared with CPU 2
  L3 Cache: 20480 KB, shared with CPU 0, 1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13,
 14, 15
Found CPU 4, with:
  L1 Cache:    32 KB, shared with CPU 5
  L2 Cache:   256 KB, shared with CPU 5
  L3 Cache: 20480 KB, shared with CPU 0, 1, 2, 3, 5, 6, 7, 8, 9, 10, 11, 12, 13,
 14, 15
Found CPU 5, with:
  L1 Cache:    32 KB, shared with CPU 4
  L2 Cache:   256 KB, shared with CPU 4
  L3 Cache: 20480 KB, shared with CPU 0, 1, 2, 3, 4, 6, 7, 8, 9, 10, 11, 12, 13,
 14, 15
Found CPU 6, with:
  L1 Cache:    32 KB, shared with CPU 7
  L2 Cache:   256 KB, shared with CPU 7
  L3 Cache: 20480 KB, shared with CPU 0, 1, 2, 3, 4, 5, 7, 8, 9, 10, 11, 12, 13,
 14, 15
Found CPU 7, with:
  L1 Cache:    32 KB, shared with CPU 6
  L2 Cache:   256 KB, shared with CPU 6
  L3 Cache: 20480 KB, shared with CPU 0, 1, 2, 3, 4, 5, 6, 8, 9, 10, 11, 12, 13,
 14, 15
Found CPU 8, with:
  L1 Cache:    32 KB, shared with CPU 9
  L2 Cache:   256 KB, shared with CPU 9
  L3 Cache: 20480 KB, shared with CPU 0, 1, 2, 3, 4, 5, 6, 7, 9, 10, 11, 12, 13,
 14, 15
Found CPU 9, with:
  L1 Cache:    32 KB, shared with CPU 8
  L2 Cache:   256 KB, shared with CPU 8
  L3 Cache: 20480 KB, shared with CPU 0, 1, 2, 3, 4, 5, 6, 7, 8, 10, 11, 12, 13,
 14, 15
Found CPU 10, with:
  L1 Cache:    32 KB, shared with CPU 11
  L2 Cache:   256 KB, shared with CPU 11
  L3 Cache: 20480 KB, shared with CPU 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 12, 13,
14, 15
Found CPU 11, with:
  L1 Cache:    32 KB, shared with CPU 10
  L2 Cache:   256 KB, shared with CPU 10
  L3 Cache: 20480 KB, shared with CPU 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13,
14, 15
Found CPU 12, with:
  L1 Cache:    32 KB, shared with CPU 13
  L2 Cache:   256 KB, shared with CPU 13
  L3 Cache: 20480 KB, shared with CPU 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 13,
14, 15
Found CPU 13, with:
  L1 Cache:    32 KB, shared with CPU 12
  L2 Cache:   256 KB, shared with CPU 12
  L3 Cache: 20480 KB, shared with CPU 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12,
14, 15
Found CPU 14, with:
  L1 Cache:    32 KB, shared with CPU 15
  L2 Cache:   256 KB, shared with CPU 15
  L3 Cache: 20480 KB, shared with CPU 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12,
13, 15
Found CPU 15, with:
  L1 Cache:    32 KB, shared with CPU 14
  L2 Cache:   256 KB, shared with CPU 14
  L3 Cache: 20480 KB, shared with CPU 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12,
13, 14
Found CPU 64, with:
  L1 Cache:    32 KB, shared with CPU 65
  L2 Cache:   256 KB, shared with CPU 65
  L3 Cache: 20480 KB, shared with CPU 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75
, 76, 77, 78, 79
Found CPU 65, with:
  L1 Cache:    32 KB, shared with CPU 64
  L2 Cache:   256 KB, shared with CPU 64
  L3 Cache: 20480 KB, shared with CPU 64, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75
, 76, 77, 78, 79
Found CPU 66, with:
  L1 Cache:    32 KB, shared with CPU 67
  L2 Cache:   256 KB, shared with CPU 67
  L3 Cache: 20480 KB, shared with CPU 64, 65, 67, 68, 69, 70, 71, 72, 73, 74, 75
, 76, 77, 78, 79
Found CPU 67, with:
  L1 Cache:    32 KB, shared with CPU 66
  L2 Cache:   256 KB, shared with CPU 66
  L3 Cache: 20480 KB, shared with CPU 64, 65, 66, 68, 69, 70, 71, 72, 73, 74, 75
, 76, 77, 78, 79
Found CPU 68, with:
  L1 Cache:    32 KB, shared with CPU 69
  L2 Cache:   256 KB, shared with CPU 69
  L3 Cache: 20480 KB, shared with CPU 64, 65, 66, 67, 69, 70, 71, 72, 73, 74, 75
, 76, 77, 78, 79
Found CPU 69, with:
  L1 Cache:    32 KB, shared with CPU 68
  L2 Cache:   256 KB, shared with CPU 68
  L3 Cache: 20480 KB, shared with CPU 64, 65, 66, 67, 68, 70, 71, 72, 73, 74, 75
, 76, 77, 78, 79
Found CPU 70, with:
  L1 Cache:    32 KB, shared with CPU 71
  L2 Cache:   256 KB, shared with CPU 71
  L3 Cache: 20480 KB, shared with CPU 64, 65, 66, 67, 68, 69, 71, 72, 73, 74, 75
, 76, 77, 78, 79
Found CPU 71, with:
  L1 Cache:    32 KB, shared with CPU 70
  L2 Cache:   256 KB, shared with CPU 70
  L3 Cache: 20480 KB, shared with CPU 64, 65, 66, 67, 68, 69, 70, 72, 73, 74, 75
, 76, 77, 78, 79
Found CPU 72, with:
  L1 Cache:    32 KB, shared with CPU 73
  L2 Cache:   256 KB, shared with CPU 73
  L3 Cache: 20480 KB, shared with CPU 64, 65, 66, 67, 68, 69, 70, 71, 73, 74, 75
, 76, 77, 78, 79
Found CPU 73, with:
  L1 Cache:    32 KB, shared with CPU 72
  L2 Cache:   256 KB, shared with CPU 72
  L3 Cache: 20480 KB, shared with CPU 64, 65, 66, 67, 68, 69, 70, 71, 72, 74, 75
, 76, 77, 78, 79
Found CPU 74, with:
  L1 Cache:    32 KB, shared with CPU 75
  L2 Cache:   256 KB, shared with CPU 75
  L3 Cache: 20480 KB, shared with CPU 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 75
, 76, 77, 78, 79
Found CPU 75, with:
  L1 Cache:    32 KB, shared with CPU 74
  L2 Cache:   256 KB, shared with CPU 74
  L3 Cache: 20480 KB, shared with CPU 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74
, 76, 77, 78, 79
Found CPU 76, with:
  L1 Cache:    32 KB, shared with CPU 77
  L2 Cache:   256 KB, shared with CPU 77
  L3 Cache: 20480 KB, shared with CPU 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74
, 75, 77, 78, 79
Found CPU 77, with:
  L1 Cache:    32 KB, shared with CPU 76
  L2 Cache:   256 KB, shared with CPU 76
  L3 Cache: 20480 KB, shared with CPU 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74
, 75, 76, 78, 79
Found CPU 78, with:
  L1 Cache:    32 KB, shared with CPU 79
  L2 Cache:   256 KB, shared with CPU 79
  L3 Cache: 20480 KB, shared with CPU 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74
, 75, 76, 77, 79
Found CPU 79, with:
  L1 Cache:    32 KB, shared with CPU 78
  L2 Cache:   256 KB, shared with CPU 78
  L3 Cache: 20480 KB, shared with CPU 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74
, 75, 76, 77, 78

Press any key to continue . . .


Using the following config file

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

    { "cpu_architecture" : "auto", "affine_to_cpu" : 64, "use_cache" : true },
    { "cpu_architecture" : "auto", "affine_to_cpu" : 66, "use_cache" : true },
    { "cpu_architecture" : "auto", "affine_to_cpu" : 68, "use_cache" : true },
    { "cpu_architecture" : "auto", "affine_to_cpu" : 70, "use_cache" : true },
    { "cpu_architecture" : "auto", "affine_to_cpu" : 72, "use_cache" : true },
    { "cpu_architecture" : "auto", "affine_to_cpu" : 74, "use_cache" : true },
    { "cpu_architecture" : "auto", "affine_to_cpu" : 75, "use_cache" : true },
    { "cpu_architecture" : "auto", "affine_to_cpu" : 76, "use_cache" : true },
    { "cpu_architecture" : "auto", "affine_to_cpu" : 77, "use_cache" : true },
    { "cpu_architecture" : "auto", "affine_to_cpu" : 78, "use_cache" : true },


],

[lebuawu2]

I don´t know, it is either 18.6.1 or 18.7.1, i didn´t try newest driver. 2000 worked on vegas 56 but didn´t work on vegas 64 when i tried, they were hashing 0. I will be back home in 10 days (i am onboard the ship) then i need to standardize my miners, drivers and settings. now it is all over the place, my rigs have miners from JCE from 31a all the way to 32g, so can´t really give any reliable information now

Thanks for your information, what is your hashrate for RX Vega 56 ?
I got around 2100 h/s for RX Vega 56 samsung chipset with cclock 1480/900, mclock 950/900, and multi_hash 1968. hynix chipset with the same setting I got around 2000 h/s.
windows 10 build 1709 amd driver 18.8.1.

[Mohondoa]

I believe this miner software is fast, because i have use this in PC mode. But never try it in GPU mode, but i believe it is also fast. Thank you dev for this software, and thank you for the update also.

[wyzdic]

Hi JCE,
Why my rig show temp and fan always 0c and 0%? Did i miss something?

[lebuawu2]

Hi JCE,
Why my rig show temp and fan always 0c and 0%? Did i miss something?

maybe you should describe more which OS (Windows 10 build 1709), driver (18.3.4), GPU (RX 580 8GB) so dev can find the root cause more easily.
for me with the details above it work fine.

[wyzdic]

Hi JCE,
Why my rig show temp and fan always 0c and 0%? Did i miss something?

maybe you should describe more which OS (Windows 10 build 1709), driver (18.3.4), GPU (RX 580 8GB) so dev can find the root cause more easily.
for me with the details above it work fine.

Windows 10 LTSB and 1709, Driver 18.4.1 and 18.6.1, RX Vega 56

Code:

 "gpu_status":
  [
    { "index": 0, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 29, "bad_shares": 0 },
    { "index": 1, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 39, "bad_shares": 0 },
    { "index": 2, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 43, "bad_shares": 0 },
    { "index": 3, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 38, "bad_shares": 0 },
    { "index": 4, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 35, "bad_shares": 0 },
    { "index": 5, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 30, "bad_shares": 0 },
    { "index": 6, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 27, "bad_shares": 0 },
    { "index": 7, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 42, "bad_shares": 0 }

[JCE-Miner]

Hello,

monero benchmarks : thanks for having added JCE I love your site and used a lot when I started mining, a lot time before i deved my own miner.

CPU counter bug: that's the first time i see that. Do you use linux version?
The CPU numbers should be in a row, but here there are gaps, I can fix it, that's a high priority bug.

Other high priority one is the Warmup sequence.
I note the bug about temp/fan but that's a lesser important bug, i'll look at this one when the other are fixed, and when i do the watchdog.

edit: i think I found the CPU counter bug, but of course i've nothing like a dual Xeon machine to test on, so it will be, once again, a blind fix.

I'm preparing a minor release with:

Code:

new coin XCash
new coin zBucks
Fixed CPU counter for dual socket CPU
Reworked warmup
More complete log about GPU

The warmup should be a bit longer (closer to 6-7 min) but more reliable. It works well on my own rigs.
The GPU log will be added to the yellow log, and specific to the GPU version, of course. You'll have info about shares and overall hashrate. I keep it separate from the purple log, because they have different meaning:

The purple is all about hardware (fan, temp, correct or bad computation)
The yellow is all about pool-side efficiency (accepted/reject shares, hashrate...)

of course a correct share tends to be accepted, and a broken one will always be rejected, but that's two different things that happens at two different places (purple: in your GPU, yellow: in your pool).

edit:
a preview

Code:

12:03:58 | Devices results - Shares Accepted/Ignored/Rejected - Average Hashrate
12:03:58 | * CPUs  - 1/0/0 - 120.48 h/s
12:03:58 | * GPU 0 - 4/0/0 - 481.93 h/s
12:03:58 | * GPU 1 - 1/0/0 - 120.48 h/s

* all CPUs are grouped, if any
* Accepted means: explicitely accepted by the pool
* Rejected means: explicitely rejected by the pool, or if --doublecheck is enabled, a broken share we didn't even try to send.
* Ignored are shares either not sent yet because of lag, or sent but the pool never answered, or we got disconnected from the pool, or the share was too stale, etc.

the hashrate is the per-device effective hashrate: only explicitely accepted shares are counted, stale/bad/outdated ones are ignored.

[JCE-Miner]

0.32h online

For windows, 32/64 and GPU

[JuanHungLo]

Hi JCE,
Why my rig show temp and fan always 0c and 0%? Did i miss something?

maybe you should describe more which OS (Windows 10 build 1709), driver (18.3.4), GPU (RX 580 8GB) so dev can find the root cause more easily.
for me with the details above it work fine.

Windows 10 LTSB and 1709, Driver 18.4.1 and 18.6.1, RX Vega 56

Code:

 "gpu_status":
  [
    { "index": 0, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 29, "bad_shares": 0 },
    { "index": 1, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 39, "bad_shares": 0 },
    { "index": 2, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 43, "bad_shares": 0 },
    { "index": 3, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 38, "bad_shares": 0 },
    { "index": 4, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 35, "bad_shares": 0 },
    { "index": 5, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 30, "bad_shares": 0 },
    { "index": 6, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 27, "bad_shares": 0 },
    { "index": 7, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 42, "bad_shares": 0 }

Double check to make sure that your AMD drivers are in COMPUTE MODE, they should display gfx901, NOT gfx900.

[wyzdic]

Hi JCE,
Why my rig show temp and fan always 0c and 0%? Did i miss something?

maybe you should describe more which OS (Windows 10 build 1709), driver (18.3.4), GPU (RX 580 8GB) so dev can find the root cause more easily.
for me with the details above it work fine.

Windows 10 LTSB and 1709, Driver 18.4.1 and 18.6.1, RX Vega 56

Code:

 "gpu_status":
  [
    { "index": 0, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 29, "bad_shares": 0 },
    { "index": 1, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 39, "bad_shares": 0 },
    { "index": 2, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 43, "bad_shares": 0 },
    { "index": 3, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 38, "bad_shares": 0 },
    { "index": 4, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 35, "bad_shares": 0 },
    { "index": 5, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 30, "bad_shares": 0 },
    { "index": 6, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 27, "bad_shares": 0 },
    { "index": 7, "temperature": 0, "fan": 0, "processor": "gfx900", "memory": 8176, "good_shares": 42, "bad_shares": 0 }

Double check to make sure that your AMD drivers are in COMPUTE MODE, they should display gfx901, NOT gfx900.

Yes, I ues "switch-radeon-gpu" to COMPUTE MODE, gfx900 is my Vega64, It does't work

[wyzdic]

0.32h online

For windows, 32/64 and GPU

API doesn't change

[lmnop]

I tried 32h with dual xeon, same error, CPU ID cannot exceed 16

[JCE-Miner]

I did no fix for the GPU fan/temp in the h version.

Xeons: sure, it was a blind fix, i've no dual xeon to test on, can you try again with --probe to see if the numbers have changed (still numbered 0-15 + 64-79 or 0-31). Thanks for report.

I tried drivers 18.8.1 on one rig and i needed to lower a lot the multi_hash (from 464 to 432) on my RX560 not to make it crash. I still prefer 18.6.1