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

[whotheff]

the attrib trick is a stealth mode to bypass some antiviruses, and it's very documented in the doc:
https://github.com/jceminer/cn_cpu_miner#privacy-and-security

It doesn't:
•Punch through your firewall: you have to open it manually if needed
•Run any command, not even attrib (see below)

hard to be closer to what you experienced
and yes it is safe and not new, just your firewall did its job

i'm not done yet for v8 because i'm writing it in assembly. i think i've room for optimizations

Thanks for clarifying that JCE!

However, I think that creating a virus like behaviour in a miner
can do only harm. A person who decided mining should
also be able to add JCE in the exclusions list of his Anti-Virus software.

Good luck with optimizations in V8, we all want them!

[UnclWish]

the attrib trick is a stealth mode to bypass some antiviruses, and it's very documented in the doc:
https://github.com/jceminer/cn_cpu_miner#privacy-and-security

It doesn't:
•Punch through your firewall: you have to open it manually if needed
•Run any command, not even attrib (see below)

hard to be closer to what you experienced
and yes it is safe and not new, just your firewall did its job

i'm not done yet for v8 because i'm writing it in assembly. i think i've room for optimizations

Thanks for clarifying that JCE!

However, I think that creating a virus like behaviour in a miner
can do only harm. A person who decided mining should
also be able to add JCE in the exclusions list of his Anti-Virus software.

Good luck with optimizations in V8, we all want them!

Sometimes it's strange situation with antiviruses. They sometime blocks attrib.exe, JCE miner exe is on exclusions, but attrib.exe is blocked...

[prvs]

I ran the little test with old rx 370 and hd 7970 cards with version 032q - worse than clay 11.3. 4x370 - 1.4kH, 5x7970 - 2.2kH; in the claymore 1.7kH and 2.4kH. No optimization with old videocards?

[UnclWish]

I ran the little test with old rx 370 and hd 7970 cards with version 032q - worse than clay 11.3. 4x370 - 1.4kH, 5x7970 - 2.2kH; in the claymore 1.7kH and 2.4kH. No optimization with old videocards?

Probably you didn't wait enough to recieve max speed. For full speed you need to wait about 10-15 minutes on JCE.

[Beruang123]

Can anyone share the best config to mine CN Heavy for RX Vega 56??
Thanks

[lebuawu2]

Can anyone share the best config to mine CN Heavy for RX Vega 56??
Thanks

you can try below config with driver 18.6.1.

{ "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":992 },
{ "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":992 },

[JCE-Miner]

If you bench against Claymore 11.3 look at the hashrate reported by the pool, because on my HD7950 rig i have a lower hashrate on screen (559 JCE against 585 Claymore per card) but a better pool hashrate.

on 2G cards (HD7850, 7870) i'm better, even on screen. i never tested on 730

[UnclWish]

If you bench against Claymore 11.3 look at the hashrate reported by the pool, because on my HD7950 rig i have a lower hashrate on screen (559 JCE against 585 Claymore per card) but a better pool hashrate.

on 2G cards (HD7850, 7870) i'm better, even on screen. i never tested on 730

On my Pitcairn 270X 4Gb Claymore 11.3 gives 550 H/s (manual modded bios with OC), JCE after start gives 500-525 H/s. After 10-15 min JCE gives 555-560 H/s.

[Primus Pilus]

how do i set difficulty for algo using jce gpu miner please?

[UnclWish]

how do i set difficulty for algo using jce gpu miner please?

Usually it's not miner settings. It must be set via pool adress or wallet name. Maybe via password. Look at your pool settings.

[Beruang123]

Can anyone share the best config to mine CN Heavy for RX Vega 56??
Thanks

you can try below config with driver 18.6.1.

{ "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":992 },
{ "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":992 },

Thank you... Can you also share for Bittube?? Really appreciate...

[bucah]

How to check reported hash rate on other miners at minexmr.com?

It is difficult for me to compare miners on that pool.

Thanks

[wyzdic]

How to check reported hash rate on other miners at minexmr.com?

It is difficult for me to compare miners on that pool.

Thanks

You can use WALLET.workerID+DIFF

[Uaciuganadu]

Hey JCE,

Can you estimate how much of a hash-rate drop we will have on CNv2?

Thank You!

[JCE-Miner]

Hey JCE,

Can you estimate how much of a hash-rate drop we will have on CNv2?

Thank You!

Hey!

I cannot give any precise number, even if the official Monero dev says about -10%.

What's new in V8:
* The tweak on variable B after the AES is removed
* But replaced by a simple XOR
* There's a new 64 bits divide/remain
* There's a new square root
* There's a new 64-bits multiply
* There are three new accesses to the scratchpad
* The main loop now have variables A, B, C and new D, while previous had only A and B, C being a temporary. It doubles the need of registers.

So i expect it to be a bit slower on 64-bits CPU since they have enough registers to handle all this, and the 64-bits divide/remain and the squareroot are all native instructions.
On 32-bits, there will be a higher performance drop, i expect, since they will run out of registers.
On GPU, both the divide and the triple access to Memory will have a big impact, i expect. Not benched yet. Because GPU memory is always asynch and such accesses to VRAM cost a lot of time. It will increase the gap between good and bad memory-equipped cards, and tighten the performance gap on cards having the same memory controller, like RX550 against RX560

Again, all this is theorical impact, i haven't finished my assembly implementation. When done i'll release the 0.33 for Windows and Linux CPU first, then the GPU version.

[bucah]

How to set the next pool when the current pool is disconnected / error? (not by minutes)

[Uaciuganadu]

Hey!

I cannot give any precise number, even if the official Monero dev says about -10%.

What's new in V8:
* The tweak on variable B after the AES is removed
* But replaced by a simple XOR
* There's a new 64 bits divide/remain
* There's a new square root
* There's a new 64-bits multiply
* There are three new accesses to the scratchpad
* The main loop now have variables A, B, C and new D, while previous had only A and B, C being a temporary. It doubles the need of registers.

So i expect it to be a bit slower on 64-bits CPU since they have enough registers to handle all this, and the 64-bits divide/remain and the squareroot are all native instructions.
On 32-bits, there will be a higher performance drop, i expect, since they will run out of registers.
On GPU, both the divide and the triple access to Memory will have a big impact, i expect. Not benched yet. Because GPU memory is always asynch and such accesses to VRAM cost a lot of time. It will increase the gap between good and bad memory-equipped cards, and tighten the performance gap on cards having the same memory controller, like RX550 against RX560

Again, all this is theorical impact, i haven't finished my assembly implementation. When done i'll release the 0.33 for Windows and Linux CPU first, then the GPU version.

Really good to know you are on top of it. But can you tell us what gains you get from doing it in assembly ?

[Sanguintan]

If you bench against Claymore 11.3 look at the hashrate reported by the pool, because on my HD7950 rig i have a lower hashrate on screen (559 JCE against 585 Claymore per card) but a better pool hashrate.

on 2G cards (HD7850, 7870) i'm better, even on screen. i never tested on 730

On my Pitcairn 270X 4Gb Claymore 11.3 gives 550 H/s (manual modded bios with OC), JCE after start gives 500-525 H/s. After 10-15 min JCE gives 555-560 H/s.

Which driver do you use?

[UnclWish]

If you bench against Claymore 11.3 look at the hashrate reported by the pool, because on my HD7950 rig i have a lower hashrate on screen (559 JCE against 585 Claymore per card) but a better pool hashrate.

on 2G cards (HD7850, 7870) i'm better, even on screen. i never tested on 730

On my Pitcairn 270X 4Gb Claymore 11.3 gives 550 H/s (manual modded bios with OC), JCE after start gives 500-525 H/s. After 10-15 min JCE gives 555-560 H/s.

Which driver do you use?

Card installed with RX 580 cards. So I always install latest driver. Now it's 18.9.3.
And I noticed that for Pitcairn R9 270X driver version didn't affects on speed at all. I checked this allready about 2 yaers and allways update driver. No one didn't change speed on 270X card.

[pbfarmer]

Can anyone share the best config to mine CN Heavy for RX Vega 56??
Thanks

you can try below config with driver 18.6.1.

{ "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":992 },
{ "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":992 },

Thank you... Can you also share for Bittube?? Really appreciate...

This is mine for a ref 64 + 56 (flashed to 64), using latest miner (32q) and latest driver (18.9.3).  Getting ~2200 + 2150:

"gpu_threads_conf" :
[
  { "mode" : "GPU", "worksize" : 16, "alpha" : 128, "beta" : 16, "index" : 3, "multi_hash":1968 },
  { "mode" : "GPU", "worksize" : 16, "alpha" : 128, "beta" : 16, "index" : 3, "multi_hash":1968 },
  { "mode" : "GPU", "worksize" : 16, "alpha" : 128, "beta" : 16, "index" : 4, "multi_hash":1968 },
  { "mode" : "GPU", "worksize" : 16, "alpha" : 128, "beta" : 16, "index" : 4, "multi_hash":1968 },
],

EDIT: sorry... these are for cn7.  But why waste a vega on heavy or variants right now?  Unless prices for TUBE or RYO or whatever come waaaay up, Vegas are better suited to cn7 coins (XMR).