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

[JCE-Miner]

so you're mining turtle or similar? that's the hardest algo to configure, i take a look and provide some config you can try.

i should release today 0.33b4 with…. +5% performance on cnv8
not a joke, but that's for Pitcairn. i benched on Tahiti and still got +3%, and +4% on Bonaire. i had no time to test on other gpus, and notably not vega.

no i didn't hack TeamRed, but i admit that gave me the clue there were a hardware +5% reserve in AMD gpus. i found it in old gpus, but maybe not in new ones.

[fluxy12]

so you're mining turtle or similar? that's the hardest algo to configure, i take a look and provide some config you can try.

i should release today 0.33b4 with…. +5% performance on cnv8
not a joke, but that's for Pitcairn. i benched on Tahiti and still got +3%, and +4% on Bonaire. i had no time to test on other gpus, and notably not vega.

no i didn't hack TeamRed, but i admit that gave me the clue there were a hardware +5% reserve in AMD gpus. i found it in old gpus, but maybe not in new ones.

Oh yes hope you can find it for rx 580 !

[UnclWish]

so you're mining turtle or similar? that's the hardest algo to configure, i take a look and provide some config you can try.

i should release today 0.33b4 with…. +5% performance on cnv8
not a joke, but that's for Pitcairn. i benched on Tahiti and still got +3%, and +4% on Bonaire. i had no time to test on other gpus, and notably not vega.

no i didn't hack TeamRed, but i admit that gave me the clue there were a hardware +5% reserve in AMD gpus. i found it in old gpus, but maybe not in new ones.

Good news! What about heavy algo?

[JCE-Miner]

please do not drop support for old maps on your miner i have better results
r7 370 2gb - monero v7 srb 1.6.9 --495h / s
 --monero v8 srb 1.6.9 --- 366h / s
                   jce 033b2 --- 422h / s
thank you very much for the miner for old video cards

Thanks, and so long, if TeamRed stay far above my miner on RX/Vega, that's what will happen, i'll focus on older cards and CPUs, were i'm the best. It may sound strange i advertise for a competitor in my own topic, but those guys deserve it, they did a really great job. When I came on v7 six month ago, there were an obsolete Claymore 11, Cast which were fast only because it was the first to use correctly the Compute Mode introduced by the beta blockchain, and SRB with perf not that better than the legacy stak/xmrig.

Here we're talking about +5% above SRB, which is already +2% mine. That's a real challenge.

0.33b4 under test, to be released soon.
Heavy: i may gain some +0.1% by backporting the v8 optims, but i'm running out of ideas to get extra speed here.

edit: i benched on my HD6950 and I get... +20% speed. Looks like the older is the card, the higher is my performance gap. It goes from +20% on HD6000 to -5% on Vega.
The 0.33b4 will probably worth to be benched on Vega, still, i may not have +20% but even a +2% would fill in the gap with SRB.

[JCE-Miner]

12:40:33 | Hashrate CPU Thread 0: 23.08 h/s
12:40:33 | Hashrate CPU Thread 1: 23.40 h/s
12:40:33 | Hashrate CPU Thread 2: 24.33 h/s
12:40:33 | Hashrate CPU Thread 3: 24.47 h/s - Total CPUs: 95.26 h/s
12:40:33 | Hashrate GPU Thread 4: 251.23 h/s
12:40:33 | Hashrate GPU Thread 5: 253.30 h/s - Total GPU 0: 504.53 h/s

That's my Core2Quad 2.666 and my RX560 2G with --auto on v8, looks like the b4 version burns like fire. It may be a false positive, but at first try, there's a noticeable perf boost even on RX. Feedbacks on other cards welcome.

[Lermite]

Great job with the 0.33b4 

GPU 0: RX 570 4G Samsung
GPU 1: RX 570 8G Micron

Code:

13:00:28 | Hashrate CPU Thread 0: 81.44 h/s
13:00:28 | Hashrate CPU Thread 1: 82.17 h/s
13:00:28 | Hashrate CPU Thread 2: 82.37 h/s
13:00:28 | Hashrate CPU Thread 3: 82.37 h/s
13:00:28 | Hashrate CPU Thread 4: 83.51 h/s
13:00:28 | Hashrate CPU Thread 5: 83.66 h/s
13:00:28 | Hashrate CPU Thread 6: 83.28 h/s
13:00:28 | Hashrate CPU Thread 7: 83.34 h/s - Total CPUs: 662.11 h/s
13:00:28 | Hashrate GPU Thread 8: 505.92 h/s
13:00:28 | Hashrate GPU Thread 9: 505.83 h/s - Total GPU 0: 1011.74 h/s
13:00:28 | Hashrate GPU Thread 10: 502.48 h/s
13:00:28 | Hashrate GPU Thread 11: 502.48 h/s - Total GPU 1: 1004.95 h/s

You're now far beyond SRB, and your miner works fine, unlike TRM that only manage to crash my graphic cards.

[JCE-Miner]

TeamRed is new, and they experience the same problems as I got at the beginning: lack of Fan/Temp monitoring, missing info in the log, stability... They don't even have colors. But i know they will add them.

Fine if i beat SRB, and since Claymore is out of v8 support, now this is TeamRed vs. JCE
I found what to do to get the +5% perfs on Vega. But not how.
My release happening one day after TR is not because of a hack (i always write my very own code) but not coincidencial, as I said, they proved there were some extra perf to pull from the AMD GPUs, and when you know something exists, so it's easier to find. But so far all my attempts on vega GPUs failed, probably because i lack some skills in Vega GCN.

I'm now a lot more confident I can fill the performance gap.

Enough GPU for now, i focus back on CPUs support.

[JCE-Miner]

0.33b4 GPU is out

Huge perf increase on CN-v8
Graft defaults to CN-v8

Hello i'm new into mining and i have one xeon skylake 12 cores, 24 threads, 56mb L3 cache and one xeon 10 cores, 20 threads with 56mb L3 cache too, in default settings i was able to get 1700h/s using cryptonight lite, is there any way to optimize my results? I was Reading about the multi hash but i don't know which config to use, and how much is the value for hugepages?

Huge pages should be enabled, on Windows 10 this is automatic if you run the miner as admin once, otherwise do it manually, here's a guide:
https://github.com/jceminer/cn_cpu_miner#large-pages

Do not mine without huge pages, the performance loss is very noticeable (like -15%)

For the threads, here's an example

Code:

"cpu_threads_conf" : 
[ 
     { "cpu_architecture" : "auto", "affine_to_cpu" : 0, "use_cache" : true, "multi_hash":2 },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 1, "use_cache" : true, "multi_hash":2 },
     ....
     { "cpu_architecture" : "auto", "affine_to_cpu" :23, "use_cache" : true, "multi_hash":2 },
]

For your 24-cpu xeon. Try it, and then apply this tweak:
* Change the first and last multi_hash (so, for CPU 0 and 23) to 1 and/or 3, and see if it's better.
* Then split the range in two (making two ranges: 0-11 and 12-23) and tweak again the respective 1st and last cpu: 0, 11, 12 and 23.
* Then split the ranges again in two (making four ranges) and again and again until you find the optimal setting.

The same applies to your 20-cpu xeon, and also the same if you mine CN-class algo (Monero, Stellite...) because you have a lot of cache
But config for Heavy would be very different, involving less threads but some no-cache mode.

[matheus176]

0.33b4 GPU is out

Huge perf increase on CN-v8
Graft defaults to CN-v8

Hello i'm new into mining and i have one xeon skylake 12 cores, 24 threads, 56mb L3 cache and one xeon 10 cores, 20 threads with 56mb L3 cache too, in default settings i was able to get 1700h/s using cryptonight lite, is there any way to optimize my results? I was Reading about the multi hash but i don't know which config to use, and how much is the value for hugepages?

Huge pages should be enabled, on Windows 10 this is automatic if you run the miner as admin once, otherwise do it manually, here's a guide:
https://github.com/jceminer/cn_cpu_miner#large-pages

Do not mine without huge pages, the performance loss is very noticeable (like -15%)

For the threads, here's an example

Code:

"cpu_threads_conf" : 
[ 
     { "cpu_architecture" : "auto", "affine_to_cpu" : 0, "use_cache" : true, "multi_hash":2 },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 1, "use_cache" : true, "multi_hash":2 },
     ....
     { "cpu_architecture" : "auto", "affine_to_cpu" :23, "use_cache" : true, "multi_hash":2 },
]

For your 24-cpu xeon. Try it, and then apply this tweak:
* Change the first and last multi_hash (so, for CPU 0 and 23) to 1 and/or 3, and see if it's better.
* Then split the range in two (making two ranges: 0-11 and 12-23) and tweak again the respective 1st and last cpu: 0, 11, 12 and 23.
* Then split the ranges again in two (making four ranges) and again and again until you find the optimal setting.

The same applies to your 20-cpu xeon, and also the same if you mine CN-class algo (Monero, Stellite...) because you have a lot of cache
But config for Heavy would be very different, involving less threads but some no-cache mode.

thx i tried to use but i don´t know how to use the -c argument, i tried -c config.txt because it´s the file that i created but it´s giving a error ''Use either the auto configuration with --auto, or manual configuration with -c <config-file>, but not both''

[JCE-Miner]

sure, remove any --auto parameter remaining, as the message says, they are mutually incompatible (because they mean the opposite of each other, --auto is for full auto, and -c for full manual)

[UnclWish]

Thanks for new version! And I hope that you find a way to improve heavy perfomance. I didn't like v8 algo - it use too much power. Even if v8 will be on the same speed as v7, heavy gives more profit, cause on 8gb cards speed on heavy algo is faster...

[matheus176]

sure, remove any --auto parameter remaining, as the message says, they are mutually incompatible (because they mean the opposite of each other, --auto is for full auto, and -c for full manual)

i´m not using the --auto that´s the problem.

[sergneo]

No support of nVidia GPU yet 

Why? will there be?

[nordmann666]

Great job with the 0.33b4 

GPU 0: RX 570 4G Samsung
GPU 1: RX 570 8G Micron

Code:

13:00:28 | Hashrate CPU Thread 0: 81.44 h/s
13:00:28 | Hashrate CPU Thread 1: 82.17 h/s
13:00:28 | Hashrate CPU Thread 2: 82.37 h/s
13:00:28 | Hashrate CPU Thread 3: 82.37 h/s
13:00:28 | Hashrate CPU Thread 4: 83.51 h/s
13:00:28 | Hashrate CPU Thread 5: 83.66 h/s
13:00:28 | Hashrate CPU Thread 6: 83.28 h/s
13:00:28 | Hashrate CPU Thread 7: 83.34 h/s - Total CPUs: 662.11 h/s
13:00:28 | Hashrate GPU Thread 8: 505.92 h/s
13:00:28 | Hashrate GPU Thread 9: 505.83 h/s - Total GPU 0: 1011.74 h/s
13:00:28 | Hashrate GPU Thread 10: 502.48 h/s
13:00:28 | Hashrate GPU Thread 11: 502.48 h/s - Total GPU 1: 1004.95 h/s

You're now far beyond SRB, and your miner works fine, unlike TRM that only manage to crash my graphic cards.

and your config?

[Lermite]

and your config?

Code:

"cpu_threads_conf": 
[ 
  { "cpu_architecture": "ryzen", "affine_to_cpu": 1, "use_cache": true, "multi_hash": 1 },
  { "cpu_architecture": "ryzen", "affine_to_cpu": 3, "use_cache": true, "multi_hash": 1 },
  { "cpu_architecture": "ryzen", "affine_to_cpu": 5, "use_cache": true, "multi_hash": 1 },
  { "cpu_architecture": "ryzen", "affine_to_cpu": 7, "use_cache": true, "multi_hash": 1 },
  { "cpu_architecture": "ryzen", "affine_to_cpu": 9, "use_cache": true, "multi_hash": 1 },
  { "cpu_architecture": "ryzen", "affine_to_cpu": 11, "use_cache": true, "multi_hash": 1 },
  { "cpu_architecture": "ryzen", "affine_to_cpu": 13, "use_cache": true, "multi_hash": 1 },
  { "cpu_architecture": "ryzen", "affine_to_cpu": 15, "use_cache": true, "multi_hash": 1 },
],

"gpu_threads_conf": 
[ 
  { "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 0, "multi_hash": 976 },
  { "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 0, "multi_hash": 976 },
  { "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 1, "multi_hash": 1008 },
  { "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 1, "multi_hash": 1008 },
]

BTW: after a longer use, the hashrate of my 4 GB (GPU 0) remains stable around 1010 h/s but the 8 GB (GPU 1)'s one ends up to 961 h/s.
But I didn't try to optimize the settings yet with the 0.33b4.

[matheus176]

i created a new file to use with the -c parameter but it´s not working i get this error everytime ''Use either the auto configuration with --auto, or manual configuration with -c <config-file>, but not both'' but i´m not using --auto, can anyone help me?

[JCE-Miner]

Please give the full command line you used so I can understand. Just replace your wallet (parameter -u) by XXX to stay anonymous

[matheus176]

Please give the full command line you used so I can understand. Just replace your wallet (parameter -u) by XXX to stay anonymous

./start.sh --archi skylake -o XXXXXXX -u XXXXXXXXXXX -p X -c config.txt

[UnclWish]

and your config?

Code:

"cpu_threads_conf": 
[ 
  { "cpu_architecture": "ryzen", "affine_to_cpu": 1, "use_cache": true, "multi_hash": 1 },
  { "cpu_architecture": "ryzen", "affine_to_cpu": 3, "use_cache": true, "multi_hash": 1 },
  { "cpu_architecture": "ryzen", "affine_to_cpu": 5, "use_cache": true, "multi_hash": 1 },
  { "cpu_architecture": "ryzen", "affine_to_cpu": 7, "use_cache": true, "multi_hash": 1 },
  { "cpu_architecture": "ryzen", "affine_to_cpu": 9, "use_cache": true, "multi_hash": 1 },
  { "cpu_architecture": "ryzen", "affine_to_cpu": 11, "use_cache": true, "multi_hash": 1 },
  { "cpu_architecture": "ryzen", "affine_to_cpu": 13, "use_cache": true, "multi_hash": 1 },
  { "cpu_architecture": "ryzen", "affine_to_cpu": 15, "use_cache": true, "multi_hash": 1 },
],

"gpu_threads_conf": 
[ 
  { "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 0, "multi_hash": 976 },
  { "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 0, "multi_hash": 976 },
  { "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 1, "multi_hash": 1008 },
  { "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 8, "index": 1, "multi_hash": 1008 },
]

BTW: after a longer use, the hashrate of my 4 GB (GPU 0) remains stable around 1010 h/s but the 8 GB (GPU 1)'s one ends up to 961 h/s.
But I didn't try to optimize the settings yet with the 0.33b4.

For 8Gb cards v7 and v8 algo multi_hash can be up to 1800+. F.e. 1664 or 1888.

[io8621]

Great job! My old rig with sapphire 370 nitro 2gb ddr5 hashing now at ~515 each card.