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

[faber0]

cryptonight_lite_v7 work on JCE?

[bluspirit]

cryptonight_lite_v7 work on JCE?

If you mean Cryptolight V7, yes. Read first page.

[nsummy]

finished cryptolight and light-v7 double hash.
worth the pain : with four doublehash on its four cores, my xeon jumps from 228 to 241 h/s, a welcome +5%

still need to do the 32 bits, and a lot of tests

You can see sorce code from XMRig or xmr-stak to look how make lowpower mode more effective.

Meanwhile, XMRig make version with Triple hash, Quard hash and Penta hash modes threads for CPU's with large amount of cache.

Yes, I have an i7-5775R that will mine cryptonightv7 at 515 H/S in 5x mode.  Its absolutely amazing.

[tanbel]

Ini sangat bermanfaat sekali bagi kami.

[JCE-Miner]

yeah, looked and saw we again had the same idea, he uses sse2 registers to avoid the lack of GPR, i already do that for cryptonight heavy and 32 bits doublehash, for the same reason. but i use one double large page, while he uses two single large pages. here we differ.

right, i'll release doublehash first, then upgrade to triple, quand, penta, maybe hexa hash.
it will still multiply the algos, i expect the binary to raise at 6M or something

cryptonight_lite_v7 work on JCE?

If you mean Cryptolight V7, yes. Read first page.

thanks, that's the --variation 4, and it's automatic with a trtlcoin wallet.

Ini sangat bermanfaat sekali bagi kami.

អរគុណ
let's both use our obscure native s-e asian language

[nsummy]

That would be awesome man.  My processor has 128 mb of L4 Cache haha

[JCE-Miner]

woow, what's that beast ? a knight landing ?

that's a lot of assembly to write, i'll probably release dual 64 bits first, then dual 32, then multiple.

[KriptoGuruTR]

CPU temperature info with report please

[griffoncoin]

Hi

I am getting "Invalid nonce; is miner not compatible with NiceHash?" and I am not mining at nicehash, is dev fees on nicehash and its not submitting and mining stays there for some time then goes back to mining on my pool




---
21:21:36 | Hashrate Thread 3: 55.27 h/s
21:21:36 | Total: 227.06 h/s
21:21:57 | Pool sends a new Job.
21:21:59 | Thread 2 finds a Share, value 120001
21:21:59 | Rejected by the pool.
21:21:59 | Message from the pool: Invalid nonce; is miner not compatible with NiceHash?
21:22:20 | Pool sends a new Job.
21:22:26 | Pool sends a new Job.
---

[JCE-Miner]

cpu temp : possible but cannot be high priority
Nicehash : nope dev fees are not to nicehash. i've nicehash specific netcode that should not be enabled if you don't use nicehash, strange. i'll proof read the netcode there may be a side effect somewhere.

what version do you use and what coin do you mine?

finished almost the 32 bits doublehash and it's better than expected, my core2 jumps from 23.2 to 26 on one core.

edit : checked and that's a legit message from pool, not devfees, maybe your pool redirect to nicehash ?
give me your pool and coin please so i can try. on the opposite, run jce with --nicehash param to see if it fixes.

Claymore has nicehash mode always enabled, maybe he's right to do so...

[Lonnegan64]

woow, what's that beast ? a knight landing ?

For sure an Intel Broadwell with 128 MB eDRAM, used as L4 cache:
http://www.cpu-world.com/CPUs/Core_i7/Intel-Core%20i7-5775C.html

[JCE-Miner]

impressive chip, do jce detect L4 at startup ? i coded it but could never try

[djkice]

getting 243.5h/s on cryptonight-heavy using Ryzen 1700X 3.84Gh/s

Any tweaks I can do to make it better?

Running on 4 threads, can I not run 8 or is it not benetifical ?


edit:

tried -t 8
16:32:32 | Hashrate Thread 0: 13.58 h/s
16:32:32 | Hashrate Thread 1: 14.47 h/s
16:32:32 | Hashrate Thread 2: 14.47 h/s
16:32:32 | Hashrate Thread 3: 14.37 h/s
16:32:32 | Hashrate Thread 4: 19.07 h/s
16:32:32 | Hashrate Thread 5: 19.12 h/s
16:32:32 | Hashrate Thread 6: 60.23 h/s
16:32:32 | Hashrate Thread 7: 60.13 h/s
16:32:32 | Total: 215.41 h/s

[JCE-Miner]

https://www.amd.com/en/products/cpu/amd-ryzen-7-1700x

close to my Rysen 1600, and yeah max perf is --auto -t 4 --archi ryzen
Heavy is the algo where, honnestly, i beat xmrig by the lowest factor, i'm less than 1% better. on 64 bits aes. on 32 bits and non aes i obliterate it.

edit: all code done for dualshare, now entering test phase.
perfs on one thread, with compared to without doublehash

core2 64 bits : +5%
core2 32 bits +11%
ryzen 64 bits : +92%
ryzen 32 bits +99%

The ryzen pipelining is impressive...

[aGeoM]

https://www.amd.com/en/products/cpu/amd-ryzen-7-1700x

close to my Rysen 1600, and yeah max perf is --auto -t 4 --archi ryzen
Heavy is the algo where, honnestly, i beat xmrig by the lowest factor, i'm less than 1% better. on 64 bits aes. on 32 bits and non aes i obliterate it.

edit: all code done for dualshare, now entering test phase.
perfs on one thread, with compared to without doublehash

core2 64 bits : +5%
core2 32 bits +11%
ryzen 64 bits : +92%
ryzen 32 bits +99%

The ryzen pipelining is impressive...

I can not wait to test the new version   

[tc_]

hey i am not sure what i am doing wrong, i took all my info from xmr-stak.

its mining monero-v7

does this product support monero-v7?

I get this error: Wallet does not match any of the supported currencies.
then it lists in red all the coins.  so i take it that this program doesn't support monero-v7.
and my wallet it the same copy/pasted from xmr-stak pools.txt file i have (it works its mining right now).

[Iamtutut]

I does support V7. I mine stellite (XTL) with.

[JCE-Miner]

yes it supports monero v7, i myself mine with it right now

params for monero v7 :

-o POOL:PORT -u WALLET -p x --variation 3 --any --auto --low

example:
-o xmrpool.eu:3333 -p x -u WALLET -p x --variation 3 --any --auto --low

Where WALLET is your wallet of course. the trick is the --any param to use.
what coin did you want to mine ? on what pool ?

[djkice]

hopefully new version is bit better on heavy xD

I was getting around 640 on stack old cryptonight algo

[JCE-Miner]

you mean old cryptonight ?
you cannot compare cryptonight classic and cryptonight heavy, the second is something like twice slower, on purpose, to annoy the ASIC. comparison must be made on same algo, same computer, same number of threads. on my ryzen 1600 stak and xmrig are at 250, jce is 252, so slightly faster but very little difference i admit. we're at hardware max both.

edit : i redid the test just for you:

getting 243.5h/s on cryptonight-heavy using Ryzen 1700X 3.84Gh/s

On my Ryzen 1600, stock, no overclock i get :

Code:

Cryptonight Variation: Cryptonight-Heavy

Starting Mining thread 0, affinity: CPU 0
Thread 0 successfully bound to CPU 0
Allocated shared Large Page at: 00000148e7200000
Allocated 4MB Cached Large Page Scratchpad Buffer for CPU 0 of NUMA node 0 at: 00000148e7400000
Starting Mining thread 1, affinity: CPU 2
Thread 1 successfully bound to CPU 2
Allocated 4MB Cached Large Page Scratchpad Buffer for CPU 2 of NUMA node 0 at: 00000148e7800000
Starting Mining thread 2, affinity: CPU 6
Thread 2 successfully bound to CPU 6
Allocated 4MB Cached Large Page Scratchpad Buffer for CPU 6 of NUMA node 0 at: 00000148e7c00000
Starting Mining thread 3, affinity: CPU 8
Thread 3 successfully bound to CPU 8
Allocated 4MB Cached Large Page Scratchpad Buffer for CPU 8 of NUMA node 0 at: 00000148e8000000
Devfee is 1.5%

20:12:36 | Connecting to mining pool pool.sumokoin.hashvault.pro:3333 ...
20:12:36 | Sumokoin (SUMO) Mining session starts!

During mining time, press:
 h    display hashrate for each mining thread.
 r    display full report.
 q    quit.

20:12:36 | Connected to pool. Now logging in...
20:12:36 | Successfuly logged as Sumoo4dRGo3cAZPajai8WbgfUZLatPKrqdsFHmfQ1vvrZrQEhSVPKMK3Jj3Qv16BgGQupDw6vEHh1jJAzYXkNScETFrNFUf354v
20:12:36 | Pool changes Difficulty to 10000.
20:12:43 | Hashrate Thread 0: 62.59 h/s
20:12:43 | Hashrate Thread 1: 62.59 h/s
20:12:43 | Hashrate Thread 2: 63.33 h/s
20:12:43 | Hashrate Thread 3: 63.31 h/s
20:12:43 | Total: 250.81 h/s

(note: the wallet is the CN-Heavy dev donation wallet, clear on purpose)
You cannot have worse perf on a OC Ryzen 1700X than my cheap stock 1600. There's a problem, maybe you run the 32-bits version?

Test on stack, exact same machine:

Code:

[2018-04-26 20:19:00] : Mining coin: sumokoin
[2018-04-26 20:19:00] : Starting 1x thread, affinity: 0.
[2018-04-26 20:19:00] : hwloc: memory pinned
[2018-04-26 20:19:00] : Starting 1x thread, affinity: 4.
[2018-04-26 20:19:00] : hwloc: memory pinned
[2018-04-26 20:19:00] : Starting 1x thread, affinity: 6.
[2018-04-26 20:19:00] : hwloc: memory pinned
[2018-04-26 20:19:00] : Starting 1x thread, affinity: 10.
[2018-04-26 20:19:00] : hwloc: memory pinned
[2018-04-26 20:19:00] : Fast-connecting to pool.sumokoin.hashvault.pro:3333 pool ...
[2018-04-26 20:19:00] : Pool pool.sumokoin.hashvault.pro:3333 connected. Logging in...
[2018-04-26 20:19:01] : Difficulty changed. Now: 10000.
[2018-04-26 20:19:01] : Pool logged in.
HASHRATE REPORT - CPU
| ID |    10s |    60s |    15m | ID |    10s |    60s |    15m |
|  0 |   62.3 |   (na) |   (na) |  1 |   62.3 |   (na) |   (na) |
|  2 |   62.1 |   (na) |   (na) |  3 |   62.1 |   (na) |   (na) |
Totals (CPU):   248.7    0.0    0.0 H/s

jce is +2h/s as expected. Really JCE is slightly (but barely) faster. Not 20% slower.