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

[indiainside]

Hi All,

What is the best setting bittube or heavy for RX 570 4g Saphire nitro ++

Also share test result hash rate for that..
Thanks.

[pbfarmer]

@pbfarmer: i'll redo some tests, but when you mine with the CPU+GPU, do you get some message like

CPU thread N finds a share, value XXX
Accepted by the pool

If yes, so the shares went to the pool, and were accepted.
I've a Ryzen + AMD RX rig so i will be able to do the exact same test.

Try pressing R key to get the effective hashare of each device. CPU should not be zero, unless it has a negligible hash speed compared to the GPUs. But a Ryzen is quite poweful.

Not that the pool connection and fee sessions are global, not per-device, so it cannot be something like CPU disconnected or stuck in fee session. Otherwise you would have zero hashrate on all devices.

please tell what coin you mine on what pool, so i can do an more precise test.

webchain: no support planned, that's not a good algo for CPU, and i don't like how they changed the CN netcode conventions just because they could. Same for Hycon. Both coins can be mined with the CPU reference xmrig fork (possibly recompiled with zero fee), or on GPU with SRB.
I may add them later, but i'm getting less dev time those days and i need to choose between what i support or not. Currently i'm finishing the Stellite v8 fork.

The rigs in question are mining heavy/variants (XHV & TUBE atm,) and the report definitely shows CPU shares accepted.  It's entirely possible it's just a coincidence that the missing effective h/r closely matches that of the actual CPU h/r, but then unfortunately, there's still an issue of effective only being ~95-96% of actual after days to weeks of uptime.  Here's a snap of the API output for my intel 2700k setup.  You can see that the effective is missing almost exactly the CPU actual h/r (though if you do add the CPU back in, effective would actually be higher than expected, given the unaccounted fee.) . I'm running a larger 8 RX 580 8G + ryzen 1600 setup in combo mode, and it's showing a ~3% diff, but it's only been up 36 hrs, so I'll run it a bit longer before reporting back.  In the past, it stabilized around a similar 4-5% offset as this one, which happens to match the actual h/r of the CPU.

Code:

{
  "hashrate":
  {
    "thread_0": 79.58,
    "thread_1": 79.53,
    "thread_2": 616.68,
    "thread_3": 616.68,
    "thread_4": 592.55,
    "thread_5": 592.92,
    "thread_6": 610.37,
    "thread_7": 610.76,
    "thread_all": [79.58, 79.53, 616.68, 616.68, 592.55, 592.92, 610.37, 610.76],
    "thread_gpu": [1233.36, 1185.47, 1221.13],
    "total": 3799.04,
    "max": 4609.50
  },
  "result":
  {
     "wallet": "hvxyCNKKzE1QvQgDkZmzUVGUgGdM1fhiD2PLffSdcp6DK3mehDx1MtRW1ZzuNxW8ppS8QQsDbeqRy5u9vSYsxkrP3ZzkY1rU3W",
     "pool": "ca.haven.miner.rocks:4005",
     "ssl": false,
     "reconnections": 163,
     "currency": "Haven (XHV)",
     "difficulty": 84531,
     "shares": 50076,
     "hashes": 1931628299,
     "uptime": "147:16:23",
     "effective": 3643.32
  },
  "gpu_status":
  [
    { "index": 0, "temperature": 40, "fan": 36, "processor": "Ellesmere", "memory": 8192, "good_shares": 16484, "bad_shares": 0 },
    { "index": 1, "temperature": 39, "fan": 39, "processor": "Ellesmere", "memory": 8192, "good_shares": 15756, "bad_shares": 0 },
    { "index": 2, "temperature": 40, "fan": 35, "processor": "Ellesmere", "memory": 8192, "good_shares": 16553, "bad_shares": 0 }
  ],
  "miner":
  {
     "version": "jce/0.33b14/gpu",
     "platform": "Intel(R) Core(TM) i7-2700K CPU @ 3.50GHz",
     "system": "Windows 64-bits",
     "algorithm": "12"
  }
}

[evlo]

I'm trying out one cnHeavy coin.

I have 12 GPUS in the windows10 rig and I have set up 88GB swap file, now my SSD in rig is almost full, but still, my last to GPUs run in single thread, i left it at 944 intensity.

Is there a way to get better performance with different multi_hash setting then 944, or even better reduce page file/swap/virtual memory usage?

[UnclWish]

I'm trying out one cnHeavy coin.

I have 12 GPUS in the windows10 rig and I have set up 88GB swap file, now my SSD in rig is almost full, but still, my last to GPUs run in single thread, i left it at 944 intensity.

Is there a way to get better performance with different multi_hash setting then 944, or even better reduce page file/swap/virtual memory usage?

You can place your pagefile into different drives. 1st part about 8-16Gb of it you must place on system drive to improove speed. Other parts you can place into any other drive via pagefile settings.

[evlo]

That answers exacly none of the questions i asked.

[abg00]

webchain supported?

[JCE-Miner]

Hello all,
quick support today

Webchain and Hycon: no support yet. I know they got more popular after the support added into Srb, but i chose to focus on the CPU-friendly algos first (Masari and Turtle), as my miner is a mixed CPU/GPU miner. Webchain and Hycon are not special, except they use a pedantically different netcode than others.

@pbfarmer :
Your new data are easier to understand.
The missing hashrate being equal to CPU is coincidental, pause your CPU and you'll see a drop will remain.
The optimal yield you can get is ~99% (100% minus the fees) but depending on your pool aggressiveness, ping and overall CPU usage you may experience lower hashrate, while 96% is somehow in the lower bound. Mining with CPU + GPU has a normally little impact on performance, but it looks like on your rig, it's higher. Maybe because of the chipset or something, or the PCIe lanes used causes some internal delays.
Try to mine with 1 and 0 Cpu and i expect you'll get a better efficiency between the instant and effective hashrate. I already experienced such on one of my rig (a A320 + ryzen). Also remove the --legacy parameter if you use it, while it may provide more stable hashrate, it tends to lower the efficiency of mixed mining.

It's very possible you get different results with another mixed miner like Stak all-in-one, just because we did different choices in term of CPU/GPU sync and netcode aggressiveness. I chose a medium/high aggressivity, but not maximum, to keep a stable hashrate and zero bad shares. It may not be the best choice in term of absolute perf on your precise rig, but that's an overall all-around design.

RX 4G on Heavy/Tube:
try this as a base, for one card

Code:

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

Then try to increase multi_hash by steps of 16

[UnclWish]

That answers exacly none of the questions i asked.

You can't recieve better speed on heavy algo than double threads with 944 multi_hash. Any other value will slower speed. And you can't reduce pagefile size. It's neccesary to have enough page file size to miner work normal. His size must be equal to size of videomemory used during miming. 2x944 multi_hash is almost 8Gb (about 7,5-7,7Gb) of videomemory during heavy algo mining.

[JCE-Miner]

online is 0.33n CPU Windows

Stellite v8 fork
Rig-id parameter (optional)

[evlo]

I thought so, I was hoping for the solution as with ETH it was previously case to have huge swap, but it was later eliminated.

[mimainer777]

Processor AMD Ryzen3 2200G
Why?

Starting CPU Thread 0, affinity: CPU 0
Thread 0 successfully bound to CPU 0
Allocated shared Large Page at: 0000018bfe000000
Failed to allocate 2MB Large Page Scratchpad Buffer, using normal memory (slower).

[RyanDokter]

Hi  I tried running JCE miner on Ubuntu 16.04 on an old 32bit dual cpu server to CPU mine Uplexa.
I have compiled the miner with my details but when i start the miner with ./start.sh i get the following:

miner@Miner:/jce_cn_cpu_miner.linux.033m$ ./start.sh

              +--------------------------------------+
              | JC Expert Cryptonote CPU Miner 0.33m |
              +--------------------------------------+


For Linux 32-bits
Analyzing Processors topology...
Dual Intel(R) Xeon(TM) CPU 3.06GHz
Assembly codename: pentium4
  SSE2    : Yes
  SSE3    : No
  SSE4    : No
  AES     : No
  AVX     : No
  AVX2    : No

Auto-configuration, selected CPUs will be highlighted...
Segmentation fault (core dumped)
miner@Miner:/jce_cn_cpu_miner.linux.033m$

Can someone please shed some light on this issue and guide me to fixing it?
 P.S I no Linux expert but with guidance can find my way through.

Thanks in advance for any help given.

[UnclWish]

Processor AMD Ryzen3 2200G
Why?

Starting CPU Thread 0, affinity: CPU 0
Thread 0 successfully bound to CPU 0
Allocated shared Large Page at: 0000018bfe000000
Failed to allocate 2MB Large Page Scratchpad Buffer, using normal memory (slower).

This can accure if you system have small amount of RAM or running too long from boot. Try to reboot and launch again.

[JCE-Miner]

P4 32 bits crash on Linux: I'll redo a test on my Core2 duo, the oldest CPU i have, but not sure at all i can reproduce the bug
Sad it would have shined since old cpu mining is my niche expertise, but maybe you use some old Linux distrib or something. It's a lot harder to support linux well because of the large variety of distribs. And i'm also more a Windows person.

Large pages, see the doc here, it needs to be manually enabled, but that's the exact same as for any other miner, so if you find a guide for xmrstak/xmrig/whatever, it will work the same.
https://github.com/jceminer/cn_cpu_miner#large-pages

[UnclWish]

P4 32 bits crash on Linux: I'll redo a test on my Core2 duo, the oldest CPU i have, but not sure at all i can reproduce the bug
Sad it would have shined since old cpu mining is my niche expertise, but maybe you use some old Linux distrib or something. It's a lot harder to support linux well because of the large variety of distribs. And i'm also more a Windows person.

Large pages, see the doc here, it needs to be manually enabled, but that's the exact same as for any other miner, so if you find a guide for xmrstak/xmrig/whatever, it will work the same.
https://github.com/jceminer/cn_cpu_miner#large-pages

JCE miner can't enable large pages if they disabled? Maybe you add this option in miner to auto-enable them like Claymore?

[RyanDokter]

P4 32 bits crash on Linux: I'll redo a test on my Core2 duo, the oldest CPU i have, but not sure at all i can reproduce the bug
Sad it would have shined since old cpu mining is my niche expertise, but maybe you use some old Linux distrib or something. It's a lot harder to support linux well because of the large variety of distribs. And i'm also more a Windows person.

Large pages, see the doc here, it needs to be manually enabled, but that's the exact same as for any other miner, so if you find a guide for xmrstak/xmrig/whatever, it will work the same.
https://github.com/jceminer/cn_cpu_miner#large-pages

As with my query above (#2261) large pages is manually activated.
I'm hoping you can help me with this.

Thanks in advance,

[zeef]

Hi JCE,

This work with webchain and hycon?

Thanks

[aazmega]

Hello JCE!
I got issue with FX 8350. Got 2 fx8350 in different MB. One doing fine with this config

"cpu_threads_conf" :
[
     { "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 },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 7, "use_cache" : true },
]

 But second one gives me error "Failed to allocate 2MB Large Page Scratchpad Buffer, using normal memory (slower)."
Same configs. Same UPlexa coin. Only difference is failed system have 4G ram and OK system got 16G ram. Is it a case or something else? Large pages are unlocked for both systems. Hashrate at monero v8 a same(~350H/s).

 Here is a log.

              +--------------------------------------+
              | JC Expert Cryptonote CPU Miner 0.33n |
              +--------------------------------------+


For Windows 64-bits
Analyzing Processors topology...
AMD FX(tm)-8350 Eight-Core Processor
Assembly codename: bulldozer
  SSE2    : Yes
  SSE3    : Yes
  SSE4    : Yes
  AES     : Yes
  AVX     : Yes
  AVX2    : No

Found CPU 0, with:
  L1 Cache:    16 KB
  L2 Cache:  2048 KB, shared with CPU 1
  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, shared with CPU 0
  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, shared with CPU 3
  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, shared with CPU 2
  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, shared with CPU 5
  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, shared with CPU 4
  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, shared with CPU 7
  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, shared with CPU 6
  L3 Cache:  8192 KB, shared with CPU 0, 1, 2, 3, 4, 5, 6

Preparing 7 Mining Threads...

+-- Thread 0 config ------------------------+
| Run on CPU:            1                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       bulldozer          |
+-------------------------------------------+

+-- Thread 1 config ------------------------+
| Run on CPU:            2                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       bulldozer          |
+-------------------------------------------+

+-- Thread 2 config ------------------------+
| Run on CPU:            3                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       bulldozer          |
+-------------------------------------------+

+-- Thread 3 config ------------------------+
| Run on CPU:            4                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       bulldozer          |
+-------------------------------------------+

+-- Thread 4 config ------------------------+
| Run on CPU:            5                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       bulldozer          |
+-------------------------------------------+

+-- Thread 5 config ------------------------+
| Run on CPU:            6                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       bulldozer          |
+-------------------------------------------+

+-- Thread 6 config ------------------------+
| Run on CPU:            7                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       bulldozer          |
+-------------------------------------------+

Cryptonight Variation: Cryptolight-uPlexa fork of Dec-2018

Low intensity.

Starting CPU Thread 0, affinity: CPU 1
Thread 0 successfully bound to CPU 1
Allocated shared Large Page at: 00000225f2a00000
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 1 of NUMA node 0 at: 00000225f2c00000

Starting CPU Thread 1, affinity: CPU 2
Thread 1 successfully bound to CPU 2
Reuse part of 2MB Cached Large Page Scratchpad Buffer at: 00000225f2d00000

Starting CPU Thread 2, affinity: CPU 3
Thread 2 successfully bound to CPU 3
Failed to allocate 2MB Large Page Scratchpad Buffer, using normal memory (slower).

Starting CPU Thread 3, affinity: CPU 4
Thread 3 successfully bound to CPU 4
Failed to allocate 2MB Large Page Scratchpad Buffer, using normal memory (slower).

Starting CPU Thread 4, affinity: CPU 5
Thread 4 successfully bound to CPU 5
Failed to allocate 2MB Large Page Scratchpad Buffer, using normal memory (slower).

Starting CPU Thread 5, affinity: CPU 6
Thread 5 successfully bound to CPU 6
Failed to allocate 2MB Large Page Scratchpad Buffer, using normal memory (slower).

Starting CPU Thread 6, affinity: CPU 7
Thread 6 successfully bound to CPU 7
Failed to allocate 2MB Large Page Scratchpad Buffer, using normal memory (slower).
Devfee for CPU is 1.5%

04:07:27 | Uplexa (UPX) Mining session starts!

[Iamtutut]

JCE, Masari fork announced: "We're preparing for a v0.3.0.0 protocol upgrade (code name Dandy Dromedary) coming in ~14 days, set for block #363,000 which will introduce SECOR (uncle mining), CNFastv2 PoW variant, and multi-output Bulletproofs (https://github.com/masari-project/masari/releases/tag/v0.3.0.0 )"

[dov17]

Collected a rig with the new Athlon 200GE processor - 2 cores / 4 threads , 4M cache (its core is from Ryzen 3, with two cores disabled). What are the correct settings V8 for this CPU?