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

[Dmitry69]

Too much "Share above target."  on pool: cryptonightv7.eu.nicehash.com:3363
config.txt:

Code:

"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 },
],
"gpu_threads_conf" : 
[ 
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":400 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":400 },
],

GPU:sapphire RX550 2GB(1071/1500@1100/1950) + CPU: XEON E5430, Hash: 490H/s + 82H/s
Win10x64(ver:1709), drv: Win7-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23.
Back on SRBminer(1.6.3) + JCE_cpu_miner.(0.31c), Hash: 482H/s + 82H/s
SRB:

Code:

"gpu_conf" : 
[ 
	{ "id" : 0, "intensity" : 24, "worksize" : 16, "threads" : 2},
]

[1715542422]

1715542422

[1715542422]

1715542422

[Iamtutut]

Thanks!

Iamtutut: The cpu and gpu version always support the same set of forks, the missing Bittube in the zip of yesterday was just a package goof i fixed.

CN bittube v4 with RX 570 4GB
Display GPU intensity 384 on both threads (C 1230Mhz; M 2100MHz)
Ohter GPUs: intensity 464. (GPU 1:1220/2020. GPU2: 1230/2025).
Total: 2053H/s. 340W at the wall

[Lonnegan64]

Thanks!

The new GPU miner 0.31c is indeed a bit faster in BitTube v4 (CN Heavy variant) than its predecessor. My Radeon RX 580 4GB @stock hashes with 672 H/s now (vs. 655 H/s with the old 0.30c). Settings are:

Code:

"gpu_threads_conf" : 
[ 
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":432 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":432 },
],

Higher intensity is not possible because a FullHD display is connected.

[Larvitar]

JCE-Miner, I'm running now the miner in my 2nd Ryzen. Is a Ryzen 5 1600 at 3.75GHz, RAM at 2933.

Is incredible! 2KH/s (just 10% less than R7 1700) mining CN-Lite V1

It's the --auto tuning the best optimisation so far to R5 1600?

[Iamtutut]

Thanks!

Iamtutut: The cpu and gpu version always support the same set of forks, the missing Bittube in the zip of yesterday was just a package goof i fixed.

CN bittube v4 with RX 570 4GB
Display GPU intensity 384 on both threads (C 1230Mhz; M 2100MHz)
Ohter GPUs: intensity 464. (GPU 1:1220/2020. GPU2: 1230/2025).
Total: 2053H/s. 340W at the wall

BTW, at some point I got 2,1KH/s, which is more than the best I've ever had with cast XMR.

[JCE-Miner]

GPU:sapphire RX550 2GB(1071/1500@1100/1950) + CPU: XEON E5430, Hash: 490H/s + 82H/s
Win10x64(ver:1709), drv: Win7-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23.
Back on SRBminer(1.6.3) + JCE_cpu_miner.(0.31c), Hash: 482H/s + 82H/s

This is a very interresting point.

Let's imagine something: Since I've dedicated netcode for Nicehash, it would be very simple for me just not to report the bad shares. I would display a correct physical 490 H/s and no reject.
Question: in such case, would you come back to JCE?

The morale to understand is about the Effective hashrate, do you get a better real-life hashrate on JCE than on other miners? A lot of user say so. Don't get too focused on error messages, and especialy not on those from Nicehash which has a very strange behavior, look at the real end results. If JCE displays more errors, maybe that's just because it never hides any one.

About nicehash, it has a zero tolerance about Stale shares. If a share gets stale a the very end of its computation, JCE doesn't drop it and still send it to Nicehash, in case it could be accepted, betting on the ping delay. If it fails, it logs the failure. Normal.

Btw, i get better results with multi_hash 432 or 464, and reaches ~518, which is crazy considering the rx550 is such a small low power card. But the RX550 and 560 depend a lot on the memory quality, my worse rx560 never went above 355h/s, which is stupid low.


I still have room for CN-Heavy optims, but i'm getting stuck with my old cards, they're close to hardware max and do not report well the speed increases. My bonaire for example is still at 268 h/s whatever i try, and claymore was also maxing at that exact same number.
On my dual HD 7950 i'm now at 1096, still behind claymore 9.7 (1146) but above other miners.

Back to CPU, JCE is supposed to be the fastest, since i'm the only dev to use dedicated assemblies for every possible combination of CPU+algo+multihash+cache+..... This is why the binary is a trillion times bigger than others. Also i've found a OpenCL optim i could port back to CPU, even the 64-bits. The hashrate may be something like +0.2% higher. Since i'm playing with the hardware max, that's a welcome improvement, yet negligeible.

JCE-Miner, I'm running now the miner in my 2nd Ryzen. Is a Ryzen 5 1600 at 3.75GHz, RAM at 2933.
It's the --auto tuning the best optimisation so far to R5 1600?

The best CN-Light/Turtle/Aeon config for R 1600 is in the github doc:

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":1 },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 2, "use_cache" : true, "multi_hash":1 },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 3, "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" : 5, "use_cache" : true, "multi_hash":1 },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 6, "use_cache" : true, "multi_hash":2 },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 7, "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" : 9, "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 },
]

This is the best configuration to mine Cryptolight, TurtleCoin or IPBC on a Ryzen 1600/1600X (12 logical CPUs, 16M cache).

IPBC is no longer Light, now it's Heavy, i need to update my doc.

[s0ftcorn]

JCE-Miner, I'm running now the miner in my 2nd Ryzen. Is a Ryzen 5 1600 at 3.75GHz, RAM at 2933.

Is incredible! 2KH/s (just 10% less than R7 1700) mining CN-Lite V1

It's the --auto tuning the best optimisation so far to R5 1600?

Im getting quite consistent over 2KH/s with my Ryzen 7 2700X for mostly any cnlite variant with the following config:

"cpu_threads_conf" :  
[  
     { "cpu_architecture" : "ryzen", "affine_to_cpu" : 0, "use_cache" : true, },
     { "cpu_architecture" : "ryzen", "affine_to_cpu" : 2, "use_cache" : true, "multi_hash" : 2, },
     { "cpu_architecture" : "ryzen", "affine_to_cpu" : 4, "use_cache" : true, "multi_hash" : 2, },
     { "cpu_architecture" : "ryzen", "affine_to_cpu" : 6, "use_cache" : true, "multi_hash" : 2, },
     { "cpu_architecture" : "ryzen", "affine_to_cpu" : 8, "use_cache" : true, },
     { "cpu_architecture" : "ryzen", "affine_to_cpu" : 10, "use_cache" : true, "multi_hash" : 2, },
     { "cpu_architecture" : "ryzen", "affine_to_cpu" : 12, "use_cache" : true, "multi_hash" : 2, },
     { "cpu_architecture" : "ryzen", "affine_to_cpu" : 14, "use_cache" : true, "multi_hash" : 2, },
]


What i basically did was to look how large the scratchpad is for cnlite (2MB) and tried to use as much of my CPUs cache for the scratchpad, thus the 6 cores doing "multi_hash": 2
I think that a ryzen is quite good for cryptonight, bad for cnheavy but exceptionally good for cnlite.

Hope this helps you to maybe squeeze a few H/s more out of your ryzen.

[nordmann666]

JCE-Miner, I'm running now the miner in my 2nd Ryzen. Is a Ryzen 5 1600 at 3.75GHz, RAM at 2933.

Is incredible! 2KH/s (just 10% less than R7 1700) mining CN-Lite V1

It's the --auto tuning the best optimisation so far to R5 1600?

Im getting quite consistent over 2KH/s with my Ryzen 7 2700X for mostly any cnlite variant with the following config:

"cpu_threads_conf" :  
[  
     { "cpu_architecture" : "ryzen", "affine_to_cpu" : 0, "use_cache" : true, },
     { "cpu_architecture" : "ryzen", "affine_to_cpu" : 2, "use_cache" : true, "multi_hash" : 2, },
     { "cpu_architecture" : "ryzen", "affine_to_cpu" : 4, "use_cache" : true, "multi_hash" : 2, },
     { "cpu_architecture" : "ryzen", "affine_to_cpu" : 6, "use_cache" : true, "multi_hash" : 2, },
     { "cpu_architecture" : "ryzen", "affine_to_cpu" : 8, "use_cache" : true, },
     { "cpu_architecture" : "ryzen", "affine_to_cpu" : 10, "use_cache" : true, "multi_hash" : 2, },
     { "cpu_architecture" : "ryzen", "affine_to_cpu" : 12, "use_cache" : true, "multi_hash" : 2, },
     { "cpu_architecture" : "ryzen", "affine_to_cpu" : 14, "use_cache" : true, "multi_hash" : 2, },
]


What i basically did was to look how large the scratchpad is for cnlite (2MB) and tried to use as much of my CPUs cache for the scratchpad, thus the 6 cores doing "multi_hash": 2
I think that a ryzen is quite good for cryptonight, bad for cnheavy but exceptionally good for cnlite.

Hope this helps you to maybe squeeze a few H/s more out of your ryzen.

dont know what you all do...my Ryzen 1700@3800MHz and 3200MHz Mem "only" get 1500hs on cnlite
tried the "best config" from JCE and also yours

[WebTosha]

Hi guys. Has anyone tried Masari on RX550 / 2 GB. I can not adjust parameters either as stable. on the buffin, the cards give out a maximum of 950 h/s for a short time and then the system drops, and 4 cards on the Lexa give out only 800 h/s and  then the system drops.

[syncro2017]

Hi guys. Has anyone tried Masari on RX550 / 2 GB. I can not adjust parameters either as stable. on the buffin, the cards give out a maximum of 950 h/s for a short time and then the system drops, and 4 cards on the Lexa give out only 800 h/s and  then the system drops.

Here is what i used, don't remember exact numbers but hash was around 900 h/s from RX550 2G Hynix

Code:

{ "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 0, "multi_hash":432 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 0, "multi_hash":432 },

[Larvitar]

Lines mining is recognised as Loki mining. Please take a look

[UnclWish]

Using cpu miner 0.31a. Algo cn-v7 on nicehash via ssl port 33363. AMD FX 8320 on two double threads. Speed about 175-190 h/s. Pool diff 100001.

Problem: Sometimes miner didn't find any share during hours! Untill restart them. All goes normal. Miner show speed, periodically recieves new jobs, no errors. But no shares for 2-3 hours?
After restarting miner, it start to find shares as must.
I think that it's due to devfee. I think that sometimes after mining devfee, it stop to find shares at all... Just thinking... But not every luanch this happens. Now I check after 20-30 minutes and if no shares finded, restart miner... This problem is on all previous versions. I just didn't try many hours before, and thinked that I'm not lucky... But after restarting miner it starts to find them.... It's strange...

[Lonnegan64]

Using cpu miner 0.31a. Algo cn-v7 on nicehash via ssl port 33363. AMD FX 8320 on two double threads. Speed about 175-190 h/s. Pool diff 100001.

Apart from your problem with the dev fee reconnect: You shouldn't use double hash with CNv7 on an AMD FX. Bulldozer has got 2 MB L2 cache per module. That's exactly the scratchpad size of one CNv7 thread. So don't us double hash, which results in 4 MB scratchpad size, use four single hash threads and put one per module, ergo (under Windows) cores 0, 2, 4 and 6 (or 1, 3, 5 and 7). That's way faster than your config. With CNv7 you should get a hashrate of approximalely 290 H/s.

The maximum you can get with an AMD FX is, to use the circumstance that it has – beneath its 2 MB L2 cache per module – an 8 MB L3 victim cache, which is not inclusive as it is the case with all Intel CPUs. Data in the L2 cache is never in the L3 cache and vice versa. So with bulldozer, you can start 8 single hash CNv7 threads dedicated to the cores 0, 1, 2, 3, 4, 5, 6 and 7. This config will result in a lot of traffic between L2 and L3, that's why performance will not scale linear with the number of threads, but still all data is cached, no slow memory access. It will give you the max. performance, in your case around 340 H/s with FX-8320.

[Uaciuganadu]

Hello Jce,

Hope you are having a good day.

I`m a big fan of your miner as it is the first one that works good with Vega and i love the way you keep making it better.

I have a small question/request that involves automatic algo switching.

I know this seems not so useful but in my case it is.

I mine on MoneroOcean, and this pool currently mines best performing V7 alt coins and pays in Monero so the profit is better. I have heard from the developer on Discord that they are planing to also add Heavy and Light coins in the mix, but only miners that support it will work. From what i can understand the miner will need to change algo on the fly from V7 to heavy for example to mine the most profitable coin. He said and i quote "Yes, working on xmrig patch now for that" so i do think that the devs of XMRig have or will have a miner that can auto switch but i do not know how they implement it.

I know that your miner compiles the code at start but would it be able to compile it for more algorithms and keep it in memory until it needs to be used?


I really think this will be the next go to miner in the future so wanted to see if this is possible.

Thank you!

[JuanHungLo]

Integrated graphics?
hooo, very important point. it means that not only my APU detection is broken but also kills the detect of other GPUs. i'll rewrite my code, thanks.

any feedback about the speed?

Has this been done yet?

p.s. I am in low power mode for the hot summer, but I am pleased with the VEGA speeds, even at 880mv for clocks and memory.

[QuirkSilver]

Too much "Share above target."  on pool: cryptonightv7.eu.nicehash.com:3363
config.txt:

Code:

"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 },
],
"gpu_threads_conf" : 
[ 
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":400 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":400 },
],

GPU:sapphire RX550 2GB(1071/1500@1100/1950) + CPU: XEON E5430, Hash: 490H/s + 82H/s
Win10x64(ver:1709), drv: Win7-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23.
Back on SRBminer(1.6.3) + JCE_cpu_miner.(0.31c), Hash: 482H/s + 82H/s
SRB:

Code:

"gpu_conf" : 
[ 
	{ "id" : 0, "intensity" : 24, "worksize" : 16, "threads" : 2},
]

Elpida 560 goes to 26 intensity (sometimes is sad with a driver/ windows combo) Hynix doesnt like 26 and can only 25. with JCE so far 432X2 or 448+416

[UnclWish]

Using cpu miner 0.31a. Algo cn-v7 on nicehash via ssl port 33363. AMD FX 8320 on two double threads. Speed about 175-190 h/s. Pool diff 100001.

Apart from your problem with the dev fee reconnect: You shouldn't use double hash with CNv7 on an AMD FX. Bulldozer has got 2 MB L2 cache per module. That's exactly the scratchpad size of one CNv7 thread. So don't us double hash, which results in 4 MB scratchpad size, use four single hash threads and put one per module, ergo (under Windows) cores 0, 2, 4 and 6 (or 1, 3, 5 and 7). That's way faster than your config. With CNv7 you should get a hashrate of approximalely 290 H/s.

The maximum you can get with an AMD FX is, to use the circumstance that it has – beneath its 2 MB L2 cache per module – an 8 MB L3 victim cache, which is not inclusive as it is the case with all Intel CPUs. Data in the L2 cache is never in the L3 cache and vice versa. So with bulldozer, you can start 8 single hash CNv7 threads dedicated to the cores 0, 1, 2, 3, 4, 5, 6 and 7. This config will result in a lot of traffic between L2 and L3, that's why performance will not scale linear with the number of threads, but still all data is cached, no slow memory access. It will give you the max. performance, in your case around 340 H/s with FX-8320.

I know all of this. My goal is not max speed from CPU. I use it just for small bonus to my GPU's. My problem is 0 shares sometimes all the time...

[nsummy]

Anyone know of a monitoring tool compatible with JCE?  I have 4 instances going and it would be much easier to look in a central location than have browser windows/ssh sessions up!

[Lermite]

dont know what you all do...my Ryzen 1700@3800MHz and 3200MHz Mem "only" get 1500hs on cnlite
tried the "best config" from JCE and also yours

My 1700@3800 and 3133 runs at more than 2680 h/s on CN Lite.

My setting is pretty simple:

Code:

{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 0, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 1, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 2, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 3, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 4, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 5, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 6, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 7, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 8, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 9, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 10, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 11, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 12, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 13, "use_cache" : true },
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 14, "use_cache" : true },    
{ "cpu_architecture" : "ryzen", "affine_to_cpu" : 15, "use_cache" : true }, 

[frozen80]

Hello miners,

I'm using the last version of JCEMiner(31c) on CNLite V7(set FORK=4 in the .bat), mining Turtlecoin.
I mine with CPU+GPU(Threadripper 1950x & Sapphire Nitro+ Vega56).

Config: https://imgur.com/JCFukAv
Hashrates on the miner:https://imgur.com/aPMszui
Hashrates on the pool: https://imgur.com/dqVebcX

The CPU is OC 10% from 3.4Ghz to 3.75Ghz.
For the Vega i'm using(1500Mhz/950mV on the gpu and 925Mhz/925mV on the memory). The Vega is serving also a fullhd display.
The full output wattage reported on the system in stand-by is 85W and when mining 330W.
The CPU itself is showing 10W in standby and around 100W when mining.
The temp of the CPU is around 60 degrees with air cooling(Noctua U12S with 2 fans).
The Vega is around 50 degrees at 2000 rpm for the fans.

I think the hashrates are good but unfortunately not a lot of coins are using this CNLite V7 fork.

Happy mining!