Topic: [XMR] JCE Miner Cryptonight/forks, now with GPU! - page 49. (Read 90841 times)

JCE 0.33a is preconfigured in advance of a few days to use Monero V2 for XMR, so yes, force it to V7 with --variation 3 until it forks, then switch to --variation 15 (or 0, or remove the parameter)

OpenCL compile: first, i apologize not to have answered the first time, i was focusing on the CPU version, and i still need to make the GPU one.
The symptom is similar to JCE running on Windows7, which is not supported, but here you're on Win10.

I tested fine on Win10 + RX560, but not with that precise version of the drivers. So i'll change one of my rig to the 18.8.1 and test again, but i won't have time immeditely, the V8 support has to be high priority.
Again, compared to xmrig or stak or other, we all use different methods of handling the OpenCL (I generate, Claymore precompiled...) so we have different level of compatibility. For example Claymore 11.3 doesn't work on the RX550, JCE does.

Please tell me what exact version of Win10 you have, to be able to reproduce the exact same way. Thanks for the detailled report

Hi,
I've been trying to run jce_cn_gpu_miner.032q and jce_cn_gpu_miner.prototype.032n on this card. I'm using Windows 10 and 18.8.1 drivers. No overclock. Card Sapphire Radeon RX 560 4GB. Help me pls.

Any thoughts on that? xmr-stak, Claymore and other GPU miners work just fine.

Ahh ok , i set variation to 3 & all working ok so, do we change it back to 0 after the fork ?

Yes, good, better than ever. V7 did two reads and two writes to memory per round. V8 does six more of each. That make the memory still more critical.
CPUs have no problem because they have prefetch, consistant memory and ultra-fast cache. GPU have almost nothing.
As I said before, even if it's very theorical, i expect V8 to close the gap between big and small GPUs having the same memory controller, like HD7850 and 7870, or RX550 and RX560.
I may be surprised if the compute cost of the new Divide and SquareRoot is really big. In such case, high-compute GPUs like Vega will be the winner, as with the old but powerfull GPUs like HD7900. To be benched.

The very precise log you gave is normal: you're mining Monero with V8 algo and it hasn't forked yet. I'll however redo a test on the 0.33a just to be sure.
To force V7 until it forks, add parameter --variation 3

The autoconfig for GPU will remain the same, because it's a safe config, not an optimal one. In short, that's 2M per GPU thread for about 80% of your video memory, and all values alpha, beta... to default. It may make it more specialized for V8, but i'll look at that later.

edit:
I retested, and here's the status:

* On Monero, you have rejected shares because Monero hasn't forked yet. Normal.
* On killallasics, their dummy wallet 9.... is detected as Fonero by JCE (because it really looks like a Fonero wallet) and so it mines with CN-classic, and produce only bad shares. Normal.

Add --variation 3 to mine Monero V7 until it forks (JCE default to V8 in advance) and --variation 15 to test on killallasics.
To mine Wownero, all is already automatic.

Hi , i get the following error on all the pools i try , even the killallasics test pool


+------------------------------------------+

+-- Thread 3 config -----------------------+
| Run on CPU:             3                |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        generic_aes      |
+------------------------------------------+

+-- Thread 4 config -----------------------+
| Run on CPU:             4                |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        generic_aes      |
+------------------------------------------+

+-- Thread 5 config -----------------------+
| Run on CPU:             5                |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        generic_aes      |
+------------------------------------------+

+-- Thread 6 config -----------------------+
| Run on CPU:             6                |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        generic_aes      |
+------------------------------------------+

+-- Thread 7 config -----------------------+
| Run on CPU:             7                |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        generic_aes      |
+------------------------------------------+

+-- Thread 8 config -----------------------+
| Run on CPU:             8                |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        generic_aes      |
+------------------------------------------+

+-- Thread 9 config -----------------------+
| Run on CPU:             10               |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        generic_aes      |
+------------------------------------------+

+-- Thread 10 config ----------------------+
| Run on CPU:             12               |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        generic_aes      |
+------------------------------------------+

+-- Thread 11 config ----------------------+
| Run on CPU:             14               |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        generic_aes      |
+------------------------------------------+

+-- Thread 12 config ----------------------+
| Run on CPU:             16               |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        generic_aes      |
+------------------------------------------+

+-- Thread 13 config ----------------------+
| Run on CPU:             17               |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        generic_aes      |
+------------------------------------------+

+-- Thread 14 config ----------------------+
| Run on CPU:             18               |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        generic_aes      |
+------------------------------------------+

+-- Thread 15 config ----------------------+
| Run on CPU:             19               |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        generic_aes      |
+------------------------------------------+

+-- Thread 16 config ----------------------+
| Run on CPU:             20               |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        generic_aes      |
+------------------------------------------+

+-- Thread 17 config ----------------------+
| Run on CPU:             21               |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        generic_aes      |
+------------------------------------------+

+-- Thread 18 config ----------------------+
| Run on CPU:             22               |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        generic_aes      |
+------------------------------------------+

+-- Thread 19 config ----------------------+
| Run on CPU:             23               |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        generic_aes      |
+------------------------------------------+

+-- Thread 20 config ----------------------+
| Run on CPU:             24               |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        generic_aes      |
+------------------------------------------+

+-- Thread 21 config ----------------------+
| Run on CPU:             26               |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        generic_aes      |
+------------------------------------------+

+-- Thread 22 config ----------------------+
| Run on CPU:             28               |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        generic_aes      |
+------------------------------------------+

+-- Thread 23 config ----------------------+
| Run on CPU:             30               |
| Use cache:              yes              |
| Multi-hash:             no               |
| Assembly module:        generic_aes      |
+------------------------------------------+

Cryptonight Variation: Cryptonight V8 fork of Oct-2018

Low intensity.

Starting CPU Mining thread 0, affinity: CPU 0
Thread 0 successfully bound to CPU 0
Allocated shared Large Page at: 0000000005200000
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 0 of NUMA node 0 at: 0
000000005400000

Starting CPU Mining thread 1, affinity: CPU 1
Thread 1 successfully bound to CPU 1
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 1 of NUMA node 0 at: 0
000000005600000

Starting CPU Mining thread 2, affinity: CPU 2
Thread 2 successfully bound to CPU 2
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 2 of NUMA node 0 at: 0
000000005c00000

Starting CPU Mining thread 3, affinity: CPU 3
Thread 3 successfully bound to CPU 3
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 3 of NUMA node 0 at: 0
000000005e00000

Starting CPU Mining thread 4, affinity: CPU 4
Thread 4 successfully bound to CPU 4
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 4 of NUMA node 0 at: 0
000000006000000

Starting CPU Mining thread 5, affinity: CPU 5
Thread 5 successfully bound to CPU 5
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 5 of NUMA node 0 at: 0
000000006200000

Starting CPU Mining thread 6, affinity: CPU 6
Thread 6 successfully bound to CPU 6
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 6 of NUMA node 0 at: 0
000000006600000

Starting CPU Mining thread 7, affinity: CPU 7
Thread 7 successfully bound to CPU 7
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 7 of NUMA node 0 at: 0
000000006800000

Starting CPU Mining thread 8, affinity: CPU 8
Thread 8 successfully bound to CPU 8
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 8 of NUMA node 0 at: 0
000000006c00000

Starting CPU Mining thread 9, affinity: CPU 10
Thread 9 successfully bound to CPU 10
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 10 of NUMA node 0 at:
0000000007000000

Starting CPU Mining thread 10, affinity: CPU 12
Thread 10 successfully bound to CPU 12
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 12 of NUMA node 0 at:
0000000007400000

Starting CPU Mining thread 11, affinity: CPU 14
Thread 11 successfully bound to CPU 14
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 14 of NUMA node 0 at:
0000000007600000

Starting CPU Mining thread 12, affinity: CPU 16
Thread 12 successfully bound to CPU 16
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 16 of NUMA node 1 at:
0000000007800000

Starting CPU Mining thread 13, affinity: CPU 17
Thread 13 successfully bound to CPU 17
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 17 of NUMA node 1 at:
0000000007a00000

Starting CPU Mining thread 14, affinity: CPU 18
Thread 14 successfully bound to CPU 18
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 18 of NUMA node 1 at:
0000000007c00000

Starting CPU Mining thread 15, affinity: CPU 19
Thread 15 successfully bound to CPU 19
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 19 of NUMA node 1 at:
0000000007e00000

Starting CPU Mining thread 16, affinity: CPU 20
Thread 16 successfully bound to CPU 20
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 20 of NUMA node 1 at:
0000000008200000

Starting CPU Mining thread 17, affinity: CPU 21
Thread 17 successfully bound to CPU 21
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 21 of NUMA node 1 at:
0000000008600000

Starting CPU Mining thread 18, affinity: CPU 22
Thread 18 successfully bound to CPU 22
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 22 of NUMA node 1 at:
0000000008800000

Starting CPU Mining thread 19, affinity: CPU 23
Thread 19 successfully bound to CPU 23
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 23 of NUMA node 1 at:
0000000008a00000

Starting CPU Mining thread 20, affinity: CPU 24
Thread 20 successfully bound to CPU 24
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 24 of NUMA node 1 at:
0000000008c00000

Starting CPU Mining thread 21, affinity: CPU 26
Thread 21 successfully bound to CPU 26
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 26 of NUMA node 1 at:
0000000009000000

Starting CPU Mining thread 22, affinity: CPU 28
Thread 22 successfully bound to CPU 28
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 28 of NUMA node 1 at:
0000000009200000

Starting CPU Mining thread 23, affinity: CPU 30
Thread 23 successfully bound to CPU 30
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 30 of NUMA node 1 at:
0000000009600000
Connecting to mining pool xmrpool.eu:3333 ...
Devfee for CPU is 1.5%

14:54:29 | Monero (XMR/XMV) Mining session starts!

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

14:54:29 | Will autoclose in 20 minutes.
14:54:29 | Connected to pool. Now logging in...
14:54:29 | Successfuly logged as 43iTLAWVGiv5T53hXS7S35ehZtvJ7zmP6gnyMqoCP66gPoq
RNiSY34TXhiaQEGiCaMe79YVzRicRA1wAnYsvTNTEJ5ojZPu
14:54:29 | Pool changes Difficulty to 10000.
14:54:30 | CPU Thread 13 finds a Share, value 10000
14:54:30 | Rejected by the pool in 47 ms.
14:54:30 | Message from the pool: Low difficulty share
14:54:30 | Your first share was rejected, you probably need to change the fork
14:54:30 | with parameter --variation N, try different values for N in [1-15]
14:54:30 | until you find the one that works.
14:54:37 | CPU Thread 8 finds a Share, value 10000
14:54:37 | Rejected by the pool in 47 ms.
14:54:37 | Message from the pool: Low difficulty share
14:54:39 | Pause All

God damn... i hope they won't make a v9 in 6 month ...

What about video memory stripes? Does video bios mods for cryptonight v7/heavy would be good for V8?

So, when I use auto config, how much is the intensity you set on Vega?

Probably not.

First, it will consume more power. I've even burnt one of my PSU during my tests, because my already power-hungry HD7950 pulled a lot more power when mining v8. So, if like me, you have ultra-fine tuned overclock and PSU, better redo all your tuning as if it was your first rig. v8 is very different.

v8 was obviously made to run fine on AES x64 cpu (because all steps are one-instruction there) and run not fine on GPU, because it involves steps GPU are bad on, typically division and random memory reads. Don't forget a GPU has something like 8G of strachpad and only 512K or 1M or 2M of cache, so all accesses are virtually uncached, and verrrryyy slow.

GPU are good to blit 128M of textures in a row, not to random access chunks of 16 bytes. That's what make CN (and still more CN-v8) CPU friendly, and GPU resistant.

Just 1 simple question regarding v8 algo setting.

Will it have the same intensity, workload, etc on Vega?

Thanks

I'm doing it right now. I'll first provide a simple implementation based on the on from the official Monero team, then i'll optimize.
It will also contain a little optim for Heavy/Tube (unrelated to v8, just i'll release it at the same time).

If you wonder why it took so long just to make the CPU version, so that's because

1. v8 is completely different from v7, i couldn't reuse anything but the implode/explode parts
2. I support 32-bits, and the 32-bits version was hell to make, because i run out of registers everywhere
3. Every x1 to x6 multihash has it own assenbly
4. the uncached version adds two more (for 64 and 32)
5. each time, there are specialization for some CPUs like core2, nehalem or ryzen

so that was about one hundred asm to update, bench and test

Thanks for your hard work! Now you must focus on GPU v8 version.

Hi!

The Windows Monero v8 CPU version is out!
https://github.com/jceminer/cn_cpu_miner

version 0.33a

I expect it to be the very fastest on 32-bits and non-aes, and in a lesser extent in 64-bits AES, the major assembly.
The Linux build comes next, then i focus on GPU, i'm getting very late now.

I read the report about the bad OpenCL. JCE openCL is generated, unlike SRB which is precompiled or stak which is static. It allows wider optim support but in case of failed build, which is very possible with generated code, please give the GPU detection log that is displayed at start, so at least i know what GPU you use.

I tested the current code (the future v8-capable) on AMD HD7000, RX, Vega and even Intel Graphics, and it compiles. I expect the failure to be caused by a different GPU or different driver version that i tested on.

However i still do very little support for now, must stay on the v8 support.

edit:
The Linux Monero v8 CPU version is out too!

What is the RAM of your GPU ? you are trying to put more than 6GB in the scratchPAD (on 1 GPU ?) if you have less than 6GB you ned to drop your multi-hash value. Check the github for suggestion with your card.

help me Compilation of OpenCL kernels failed.
Error: CL_BUILD_PROGRAM_FAILURE Code: O-2.10
 
Starting GPU Mining thread 0, on GPU 1
Created OpenCL Context for GPU 1 at 000001b693433c40
Created OpenCL Thread 0 Command-Queue for GPU 1 at 000001b6933169c0
Scratchpad Allocation success for OpenCL Thread 0
Allocating big 3072MB scratchpad for OpenCL Thread 0...
Compiling kernels of OpenCL Thread 0...
Compilation of OpenCL kernels failed.
Error: CL_BUILD_PROGRAM_FAILURE Code: O-2.10

Starting GPU Mining thread 1, on GPU 1
Created OpenCL Thread 1 Command-Queue for GPU 1 at 000001b693316720
Scratchpad Allocation success for OpenCL Thread 1
Allocating big 3072MB scratchpad for OpenCL Thread 1...
Compiling kernels of OpenCL Thread 1...
Compilation of OpenCL kernels failed.
Error: CL_BUILD_PROGRAM_FAILURE Code: O-2.10
Devfee for GPU is 0.9%

16:56:34 | OpenCL Thread 1 failed, Stop.
16:56:34 | Connecting to mining pool stellite.ingest-asia.cryptoknight.cc:16222 ...
16:56:34 | Stellite (XTL) Mining session starts!

During mining time, press:
 h      display hashrate for each mining thread.
 r      display full report.
 p      pause all.
 u      pause CPUs.
 0-F    pause GPU 0-15.
 t      GPU temperature and fan speed.
 q      quit.

16:56:34 | GPU Compute allocation starts at 80% and reaches 100% after ~5min,
16:56:34 | during this time, the hashrate may be unstable and inconsistent.
16:56:34 | Let the miner warm-up if you're tuning for performance.
16:56:34 | Unloaded OpenCL kernels of GPU Thread 1
16:56:34 | OpenCL Thread 0 failed, Stop.
16:56:34 | Unloaded OpenCL kernels of GPU Thread 0
16:56:34 | Released OpenCL Thread 1 Scratchpad at 000001b698146d40
16:56:34 | Released OpenCL Thread 0 Scratchpad at 000001b6933e7580
16:56:34 | Released OpenCL Thread 1 Command-Queue of GPU 1 at 000001b693316720
16:56:34 | Released OpenCL Thread 0 Command-Queue of GPU 1 at 000001b6933169c0
16:56:34 | Released OpenCL Context 000001b693433c40 of GPU 1
16:56:34 | Connected to pool. Now logging in...
16:56:34 | Successfuly logged as Se3zVwDh8JdKPqXyDWqjQVQFbSGX9oLs7YQHAyTqtyDbQATZmg4Jc1vH2vnhz4kcqo6mnVT4AwfMv8R rJxKwH7mk3A6Sc1vDU
16:56:34 | Pool connection socket closed.
16:56:34 | Mining thread 0 stopped.
16:56:34 | Mining thread 1 stopped.
Press any key to continue . . .

Thanks.  i get lower hashrate with that 16 core config as below on xmr (~750).  Perhaps due to dual channel ram.


for cn-lite I already have enabled all logical cores and multi_hash:2 for 4 core; 0,6,12,18

Are there messages before the reject that say "stale share, may be rejected by the pool" ?
If yes, so here's the answer. We all have different netcode aggresivity about stale shares, it's very possible JCE is more aggressive than other, like Claymore or SRB. Please look at your pool to see if your effective hashrate is better with JCE, even with the rejecteed shares, if yes, so it's still a good deal for you.

Also try to lower the multi_hash parameter, it sometimes helps, but may also make the miner slower, so do the math if it worth to be changed.

CPU version to be released very soon, i'm testing it right now.
GPU will come next.

Hello, is there a JCE miner update coming for the new algorithm coming soon?

Some times miner say "low difficulty share" and "rejected by pool"

my setting

jce_cn_gpu_miner64.exe --auto --any --no-cpu --forever --variation 12 --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %*

in other miner programs, there is no such problem

exp: SRB Miner

whats wrong ?