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

[Lonnegan64]

K8-K10 bug fixed

please update, unless you use AES or 32-bits, in such case JCE 0.19 and 0.20 are the exact same.

Addendum: the bug is fixed mining Aeon, but when mining TurtleCoin with dual-mining-feature, I still get rejected shares. Not using dual-mining, everything is fine even with TurtleCoin. So there must be a small bug somewhere

Edit: this time it has nothing to do with the K10. Lynnfield produces the same rejected shares as soon as I use dual-mining with TurtleCoin

[shiroocrypto]

Are there builds for systems other than windows? ... For my windows work machine, they're very strict on apps (so this is reporting as malware/virus which I don't believe) ... So i want to try and run it in a linux virtual machine

Given that, I could not inspect the zip file ... but is there a way to provide a linux executable?

[skablast]

Jce miner can't use Huge pages even if present, recognized by windows
Can be that doesn't like the fact that huge pages are on drive d: instead of c: ?

[JCE-Miner]

i tried this on xeon haswell i got 155 hash for cryptonight heavy. xmrstak got 165 hash

How many cores and cache do you have ? It may be the doublehash that gives big boost to stak, it's good on high cache cpu, and xeon are.

Jce miner can't use Huge pages even if present, recognized by windows
Can be that doesn't like the fact that huge pages are on drive d: instead of c: ?

seems you're talking about Pagefile. Huge pages are in memory, not related to Pagefile (aka swap)

If you run Windows 10 pro, run jce as admin once, reboot and it should be enabled. Otherwise look at this guide
https://technet.microsoft.com/en-us/library/ms190730(v=sql.105).aspx  

Jce tries to connect 5 times before it gives up. You can loop in a .bat if you want to try forever.

I note the dual thread bug, not as bad because it's rarely used, but needs to fix.

Ho, and the Linux version : Planned but not ready yet. All miners are detected as virus or Trojan, but they aren't, not jce nor any other.

[skablast]

Thanks.

Lost in translation, by windows italiano and me

[JCE-Miner]

Thanks.

Lost in translation, by windows italiano and me

I just noticed, thanks to your post, that i use the term Huge instead of Large. To be fixed in doc and binaries.
I'm testing right now the 64-bits cryptonight heavy non-aes. I can lose against stak on some recent Intel cpu i haven't optimized for, but on non-aes.

edit: on my Xeon (autoconfig, core2 base, no aes, 64 bits)

Code:

20:27:19 | Hashrate Thread 0: 12.65 h/s
20:27:19 | Hashrate Thread 1: 12.65 h/s
20:27:19 | Hashrate Thread 2: 12.64 h/s
20:27:19 | Hashrate Thread 3: 12.80 h/s
20:27:19 | Total: 50.73 h/s

Stak 2.4.2 (auto config, all Large Page enabled)

Code:

HASHRATE REPORT - CPU
| ID |    10s |    60s |    15m | ID |    10s |    60s |    15m |
|  0 |    8.2 |   (na) |   (na) |  1 |    8.2 |   (na) |   (na) |
|  2 |    8.4 |   (na) |   (na) |  3 |    8.4 |   (na) |   (na) |
Totals (CPU):    33.1    0.0    0.0 H/s

JCE is just... 50% faster on non-aes.
On Haswell... yeah i don't own a modern Intel cpu, only amd, hence why there's a Ryzen assembly, but no Haswell. Very possible Stak is still better on Haswell. I guarantee jce is faster on non-aes, 32-bits and on ryzen. Cannot be sure for others 64-bits AES. And even on Ryzen, i'm just 1% faster.

this time it has nothing to do with the K10. Lynnfield produces the same rejected shares as soon as I use dual-mining with TurtleCoin

Good diagnostic, i found the bug, and yes, unrelated to the K8-K10 bug. That's a thread sync problem. So bad it can freeze the miner. I'm fixing, should be done rapidly.

[JCE-Miner]

Version 0.21

Code:

Maximum number of threads is now 64 (was 32 before)
Nicehash defaults to Cryptonight V7
Fixed the dual-thread bug
Noticeable performance increase +1% on V7, V7-light and Cryptonight Heavy
AES-32 bits still faster, even with original CN
Fixed detection of Lynfield

Now JCE is as fast on CN-V7 than others on original CN, at least on my Ryzen : 502h/s

[aGeoM]

Hi

Just finish testing dualmining as you recommended, the good news, shares are accepted, the bad news hash decreased to 128 and system freezes after a couple minutes.

Gonna test 0.21 right now.

Thanks.

[JCE-Miner]

Hi

Just finish testing dualmining as you recommended, the good news, shares are accepted, the bad news hash decreased to 128 and system freezes after a couple minutes.

Gonna test 0.21 right now.

Thanks.

The bug was very bad and could lead to a freeze or crash, so i guess (and hope) it's fixed in 0.21
The only CPU so far where i saw a perf increase was a core2 duo Conroe (2 cores, 2M cache).
In earlier version of JCE (pre-bitcointalk) there were a triple and quad thread mode that was never better than simple thread, so i dropped it.
I could drop dual if it really never gives a perf increase, except of the very sole Conroe.

[aGeoM]

I am testing 0.21 normal 6T --low no dualminig all good same hash.

Gonna try dualminig next, as I said a got freezes on the firsts minutes so the hash reading was at the start not so accurate. I will report my findings.  


EDIT

10min run, no freezes hash 140H/s

http://www.bild.me/bild.php?file=9475035JCE0.21-PIIX6-6T-LOW-DM-OC.jpg

[Lonnegan64]

The only CPU so far where i saw a perf increase was a core2 duo Conroe (2 cores, 2M cache).

Dual mining is perfect for AMD Phenom II X4. It has an L3 cache of 6 MB, so 3 cryptonight threads fit into it. But is has 4 cores, so with a normal miner, one core is without a job. Thanks to dual mining I can fill the L3 with 3 threads and add a "helper thread" to the 4th core. It looks like this:

"cpu_threads_conf" :
[
     { "cpu_architecture" : "deneb", "affine_to_cpu" : 0, "use_cache" : true },
     { "cpu_architecture" : "deneb", "affine_to_cpu" : 1, "use_cache" : true },
     { "cpu_architecture" : "deneb", "affine_to_cpu" : 2, "use_cache" : true },
     { "cpu_architecture" : "deneb", "affine_to_cpu" : 3, "use_cache" : true, "dual_mine_with": 2 },
]

Without dual mining the Phenom II X4 905e hashes up to 58 H/s. Thanks to dual mining on the last core, it's 64 H/s

[UnclWish]

I'm awaiting dual/double threads.

[KriptoGuruTR]

Intel® Core i5-6600 Processor

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

start.bat exe line

Code:

C:\Users\User\Desktop\jce_cn_cpu_miner.021\jce_cn_cpu_miner%BITS%.exe -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %* -c config.txt --variation 4 --low

640 H/S at 30 watts, monero

I always get "Low difficulty share" error. I tried different difficulties, no change. Any ideas?

Thanks

[aGeoM]

The only CPU so far where i saw a perf increase was a core2 duo Conroe (2 cores, 2M cache).

Dual mining is perfect for AMD Phenom II X4. It has an L3 cache of 6 MB, so 3 cryptonight threads fit into it. But is has 4 cores, so with a normal miner, one core is without a job. Thanks to dual mining I can fill the L3 with 3 threads and add a "helper thread" to the 4th core. It looks like this:

"cpu_threads_conf" :
[
     { "cpu_architecture" : "deneb", "affine_to_cpu" : 0, "use_cache" : true },
     { "cpu_architecture" : "deneb", "affine_to_cpu" : 1, "use_cache" : true },
     { "cpu_architecture" : "deneb", "affine_to_cpu" : 2, "use_cache" : true },
     { "cpu_architecture" : "deneb", "affine_to_cpu" : 3, "use_cache" : true, "dual_mine_with": 2 },
]

Without dual mining the Phenom II X4 905e hashes up to 58 H/s. Thanks to dual mining on the last core, it's 64 H/s

I setup my PhenomII 955 @stock and I got 94-98H/s, startupconfig on SS.

PhenomII X4 Hash

[UnclWish]

Intel® Core i5-6600 Processor

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

start.bat exe line

Code:

C:\Users\User\Desktop\jce_cn_cpu_miner.021\jce_cn_cpu_miner%BITS%.exe -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %* -c config.txt --variation 4 --low

640 H/S at 30 watts, monero

I always get "Low difficulty share" error. I tried different difficulties, no change. Any ideas?

Thanks

You set algo variation 4 - this is cryptolightV7. Check your pool address and port. Did you right chose algo for your pool and port? Maybe you want to cryptonightV7? This is 3 variation algo...

[skablast]

Can I dualmine with an intel13 6100 ?
Just because mining stellite, the pool doesn't accept difficulty lower than 15 k and sometimes I got kicked out

[JCE-Miner]

Thanks, I was just typing that exact same answer : Monero is variation 3. Use --help to get the list of variations.

Without dual mining the Phenom II X4 905e hashes up to 58 H/s. Thanks to dual mining on the last core, it's 64 H/s

It warms up my heart at least somebody uses the dual thread  
Next priority now is dual-share, which is the exact opposite (for cpu with more cache than threads, like Xeon)

About Xeon, note the thread limit is now 64, so the 40-core config we discussed here can be merged into one single JCE instance.

You can try dualmine, the config example above is good, the trick is often to dualmine the last thread with the one before
https://ark.intel.com/fr/products/90729/Intel-Core-i3-6100-Processor-3M-Cache-3_70-GHz

For you, I advise (with no way to be sure)

Code:

"cpu_threads_conf" :
[
     { "cpu_architecture" : "auto", "affine_to_cpu" : 0, "use_cache" : true },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 1, "use_cache" : true, "dual_mine_with": 0 },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 2, "use_cache" : true },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 3, "use_cache" : true, "dual_mine_with": 2 },
]

edit:

I setup my PhenomII 955 @stock and I got 94-98H/s, startupconfig on SS.

Four threads ? So it's better to use 4 normal threads than 3 + dualmine ? [heart broken]
If that's what you say, so it's another proof the dual mine is useless outside the very rare case of a 2M-cache dual core cpu.

About the core i3 : before tweaking the dual thread, try with a simple -t 4 param to force four threads. It may simply be the best config.

[KriptoGuruTR]

Intel® Core i5-6600 Processor

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

start.bat exe line

Code:

C:\Users\User\Desktop\jce_cn_cpu_miner.021\jce_cn_cpu_miner%BITS%.exe -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %* -c config.txt --variation 4 --low

640 H/S at 30 watts, monero

I always get "Low difficulty share" error. I tried different difficulties, no change. Any ideas?

Thanks

You set algo variation 4 - this is cryptolightV7. Check your pool address and port. Did you right chose algo for your pool and port? Maybe you want to cryptonightV7? This is 3 variation algo...

--variation 3 solved the problem, thanks

Total: 151.19 h/s with --low, europe.cryptonight-hub.miningpoolhub.com port 20580, start difficulty 40000

I am going to run it for 1 hour and see the results.

[aGeoM]

Four threads ? So it's better to use 4 normal threads than 3 + dualmine ? [heart broken]
If that's what you say, so it's another proof the dual mine is useless outside the very rare case of a 2M-cache dual core cpu.

I did not test dual mine on the X4 I was happy to see almost 100H/s against 45H/s before with XmRig/Stak.

Keep your ❤️ warm 😁

What I tried was setting dual mine on my Ryzen as the nine thread, but it gave a error about. AES CPU found.

[JCE-Miner]

Dual mine forbidden with AES and Cryptonight Heavy.
AES because it's always far worse than regular threads, Heavy because there's no longer smooth parts in cryptonight version Heavy, so threads have no longer any resource to share.

Dual is for non-aes, C-Night[v7], C-Light[v7], 32 or 64 bits.