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

I'm also waiting with this one to work with JCE.

hi, add --forever --keepalive to your cmd line when starting jce miner.

M/

I'm using fixed difficulty, but I think the main problem is the linux JCE just goes to command line after IP ban instead of reconnecting. It should keep trying to reconnect to the pool.

Is it a quite weak machine? I had that problem a while ago with Monero and some older machines. The pool rised the difficulty higher and higher till the machine had no chance to return a hash in the given time. As a solution, I added the smallest allowed difficulty after the wallet address in the config file. With your pool it should be ".100000"

I sometimes get booted from pool with latest linux version of JCE cpu miner. Am mining Turtlecoin to Steadyhash pool.

miner: jce_cn_cpu_miner.linux.033q.zip
os: ubuntu 16.04 & 18.04
log:
07:58:04 | Rejected by the pool in 54 ms.
07:58:04 | Connection failed: The pool kicked you out as Unauthenticated, its Difficulty 600023 is probably too high for your computing power. If the pool allows fixed Difficulty, fix it to a lower value.
07:58:04 | Connection interrupted, waiting 5s then retry, attempt #1
07:58:04 | Connection failed: Socket receive error: socket explicitly closed by the pool
07:58:04 | Connection interrupted, waiting 5s then retry, attempt #2
07:58:09 | Connecting to mining pool trtl.steadyhash.org:3853 ...
07:58:10 | Connecting to mining pool trtl.steadyhash.org:3853 ...
07:58:10 | Connected to pool. Now logging in...

Had 3 different ubuntu machines mining to same pool. When I woke up I saw it was at the ubuntu command line on all 3 machines instead of actually logging in.

Note that I got some windows machines on xmrig that don't seem to experience this issue.
Unsure if pool or jce is the cause.

Wow, with floating point operations!   That should keep away ASICs for a loooong time  

JCE, monero is forking in one month too...

https://www.reddit.com/r/Monero/comments/ap6iiw/monero_will_fork_at_block_1788000_march_9th/

JCE please note:

RYO is going to fork with a new algo "CN GPU": Fork Block: 228750 @ Feb 14th 2019 UTC 12.00

Github: https://github.com/ryo-currency/ryo-currency/pull/163
Testpool: https://tnpool.ryo-currency.com/

- Cryptonight Webchain ??

Hi again, your avx code path is buggy, look at this:

Analyzing Processors topology...
Intel(R) Core(TM) i5-3330 CPU @ 3.00GHz
Assembly codename: generic_aes_avx
  SSE2    : Yes
  SSE3    : Yes
  SSE4    : Yes
  AES     : Yes
  AVX     : Yes
  AVX2    : No

Found CPU 0, with:
  L1 Cache:    32 KB
  L2 Cache:   256 KB
  L3 Cache:  6144 KB, shared with CPU 1, 2, 3
Found CPU 1, with:
  L1 Cache:    32 KB
  L2 Cache:   256 KB
  L3 Cache:  6144 KB, shared with CPU 0, 2, 3
Found CPU 2, with:
  L1 Cache:    32 KB
  L2 Cache:   256 KB
  L3 Cache:  6144 KB, shared with CPU 0, 1, 3
Found CPU 3, with:
  L1 Cache:    32 KB
  L2 Cache:   256 KB
  L3 Cache:  6144 KB, shared with CPU 0, 1, 2

Preparing 3 Mining Threads...

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

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

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

Cryptonight Variation: Cryptonight-Stellite/Masari V8


Starting CPU Thread 0, affinity: CPU 0
Thread 0 successfully bound to CPU 0
Allocated shared Large Page at: 0x7fa0aea00000
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7fa0ae800000

Starting CPU Thread 1, affinity: CPU 1
Thread 1 successfully bound to CPU 1
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7fa0adc00000

Starting CPU Thread 2, affinity: CPU 2
Thread 2 successfully bound to CPU 2
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7fa0ad000000
Devfee for CPU is 1.5%

15:23:25 | Masari (MSR) Mining session starts!

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

15:23:26 | Connecting with SSL to mining pool pool.masari.hashvault.pro:443 ...
15:23:26 | Connected to pool. Now logging in...
15:23:26 | Successfuly logged as xxx
15:23:26 | Pool changes Difficulty to 9000.
15:23:56 | Hashrate CPU Thread 0: 70.08 h/s
15:23:56 | Hashrate CPU Thread 1: 57.92 h/s
15:23:56 | Hashrate CPU Thread 2: 72.19 h/s
15:23:56 | Total: 200.19 h/s - Max: 200.19 h/s
15:23:59 | Pool sends a new Job.
15:24:00 | CPU Thread 1 finds a Share, value 9000
15:24:00 | Accepted by the pool in 82 ms.
15:24:31 | CPU Thread 1 finds a Share, value 9000
15:24:31 | Accepted by the pool in 50 ms.
15:24:33 | Pool sends a new Job.
15:25:00 | Pool changes Difficulty to 5790.
15:25:24 | CPU Thread 1 finds a Share, value 5790
15:25:24 | Accepted by the pool in 50 ms.
15:25:24 | CPU Thread 0 finds a Share, value 5790
15:25:24 | Accepted by the pool in 47 ms.
15:25:25 | Hashrate CPU Thread 0: 72.83 h/s
15:25:25 | Hashrate CPU Thread 1: 51.36 h/s
15:25:25 | Hashrate CPU Thread 2: 71.62 h/s
15:25:25 | Total: 195.80 h/s - Max: 200.19 h/s

Can you look at it please? Thank you! Milan

Hi JCE, here are results with the same (suggested) config as xmr-stak on CNv8:

Analyzing Processors topology...
Intel(R) Core(TM) i5-3330 CPU @ 3.00GHz
Assembly codename: generic_aes_avx
  SSE2    : Yes
  SSE3    : Yes
  SSE4    : Yes
  AES     : Yes
  AVX     : Yes
  AVX2    : No

Found CPU 0, with:
  L1 Cache:    32 KB
  L2 Cache:   256 KB
  L3 Cache:  6144 KB, shared with CPU 1, 2, 3
Found CPU 1, with:
  L1 Cache:    32 KB
  L2 Cache:   256 KB
  L3 Cache:  6144 KB, shared with CPU 0, 2, 3
Found CPU 2, with:
  L1 Cache:    32 KB
  L2 Cache:   256 KB
  L3 Cache:  6144 KB, shared with CPU 0, 1, 3
Found CPU 3, with:
  L1 Cache:    32 KB
  L2 Cache:   256 KB
  L3 Cache:  6144 KB, shared with CPU 0, 1, 2

Preparing 3 Mining Threads...

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

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

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

Cryptonight Variation: Cryptonight-Stellite/Masari V8


Starting CPU Thread 0, affinity: CPU 0
Thread 0 successfully bound to CPU 0
Allocated shared Large Page at: 0x7f26b0c00000
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7f26b0a00000

Starting CPU Thread 1, affinity: CPU 1
Thread 1 successfully bound to CPU 1
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7f26a3e00000

Starting CPU Thread 2, affinity: CPU 2
Thread 2 successfully bound to CPU 2
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7f26a3200000
Devfee for CPU is 1.5%

14:33:26 | Masari (MSR) Mining session starts!

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

14:33:26 | Connecting with SSL to mining pool pool.masari.hashvault.pro:443 ...
14:33:27 | Connected to pool. Now logging in...
14:33:27 | Successfuly logged as xxx
14:33:27 | Pool changes Difficulty to 9000.
14:33:57 | Hashrate CPU Thread 0: 17.27 h/s
14:33:57 | Hashrate CPU Thread 1: 14.99 h/s
14:33:57 | Hashrate CPU Thread 2: 16.76 h/s
14:33:57 | Total: 49.01 h/s - Max: 49.01 h/s
....
14:52:15 | Pool pool.masari.hashvault.pro:443 (SSL)
14:52:15 | Reconnections 0
14:52:15 | Currency Masari (MSR)
14:52:15 | Current pool Difficulty 5000
14:52:15 | Accepted Shares 4
14:52:15 | Total Hashes 28000
14:52:15 | Miner uptime 0:18:49
14:52:15 | Effective net hashrate 24.80 h/s
...
14:59:45 | Hashrate CPU Thread 0: 17.41 h/s
14:59:45 | Hashrate CPU Thread 1: 15.07 h/s
14:59:45 | Hashrate CPU Thread 2: 16.29 h/s
14:59:45 | Total: 48.76 h/s - Max: 49.26 h/s


Something is wrong here I think...

Thank you!

Hi, with suggested config it is worse This is best what I can get. Will post details later, I've kid in care now xmr-stak can't mine CNfast_V8 now.

Thank you for reply.

Milan

Hello,

Sure it would be helpful to get comparison with same algo...
stak mines with 3 threads with 2M cache each, for your total of 6M cache, which sounds good.

What happens if you mine with the same configuration with JCE ?
multi_hash:1 on three CPUs: 0, 1 and 2?

I'd expect you get at least on par results, not -40%.
Your current config using only 2 cores and 8M cache (2M overflood) is expected to be bad.

Hi, yes I know but CNFastv8 is faster than CNv8 thus I should get +40% more HR not -40% XMR example only demonstrates real HS on CNv8 with this CPU...

Hi JCE, I've strange performance problem on one avx machine, JCE minig MSR is 2times slower as xmrstak minig XMR. Hmmm. Any sugestions? Config line: -o pool.masari.hashvault.pro:443 -u xxx -p db -c ./config.jce --variation 21 --ssl --forever

Changing threads count, multihash all tried but this is maximum what I can get out of this.

Thank you.


Analyzing Processors topology...
Intel(R) Core(TM) i5-3330 CPU @ 3.00GHz
Assembly codename: generic_aes_avx
  SSE2    : Yes
  SSE3    : Yes
  SSE4    : Yes
  AES     : Yes
  AVX     : Yes
  AVX2    : No

Found CPU 0, with:
  L1 Cache:    32 KB
  L2 Cache:   256 KB
  L3 Cache:  6144 KB, shared with CPU 1, 2, 3
Found CPU 1, with:
  L1 Cache:    32 KB
  L2 Cache:   256 KB
  L3 Cache:  6144 KB, shared with CPU 0, 2, 3
Found CPU 2, with:
  L1 Cache:    32 KB
  L2 Cache:   256 KB
  L3 Cache:  6144 KB, shared with CPU 0, 1, 3
Found CPU 3, with:
  L1 Cache:    32 KB
  L2 Cache:   256 KB
  L3 Cache:  6144 KB, shared with CPU 0, 1, 2

Preparing 2 Mining Threads...

+-- Thread 0 config ------------------------+
| Run on CPU:            0                  |
| Use cache:             yes                |
| Multi-hash:            x2                 |
| Assembly module:       generic_aes_avx    |
+-------------------------------------------+

+-- Thread 1 config ------------------------+
| Run on CPU:            1                  |
| Use cache:             yes                |
| Multi-hash:            x2                 |
| Assembly module:       generic_aes_avx    |
+-------------------------------------------+

Cryptonight Variation: Cryptonight-Stellite/Masari V8


Starting CPU Thread 0, affinity: CPU 0
Thread 0 successfully bound to CPU 0
Allocated shared Large Page at: 0x7f92b9800000
Allocated 4MB Cached Large Page Scratchpad Buffer at: 0x7f92b9400000

Starting CPU Thread 1, affinity: CPU 1
Thread 1 successfully bound to CPU 1
Allocated 4MB Cached Large Page Scratchpad Buffer at: 0x7f92b8600000
Devfee for CPU is 1.5%

08:57:13 | Masari (MSR) Mining session starts!

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

08:57:14 | Connecting with SSL to mining pool pool.masari.hashvault.pro:443 ...
08:57:14 | Connected to pool. Now logging in...
08:57:14 | Successfuly logged as xxx
08:57:14 | Pool changes Difficulty to 9000.
08:57:26 | Pool sends a new Job.
08:57:27 | Hashrate CPU Thread 0: 36.12 h/s
08:57:27 | Hashrate CPU Thread 1: 33.31 h/s
08:57:27 | Total: 69.42 h/s - Max: 69.42 h/s
08:57:50 | Hashrate CPU Thread 0: 35.90 h/s
08:57:50 | Hashrate CPU Thread 1: 33.14 h/s
08:57:50 | Total: 69.04 h/s - Max: 69.42 h/s
08:57:57 | Pool sends a new Job.

08:58:11 | Hashrate CPU Thread 0: 35.90 h/s
08:58:11 | Hashrate CPU Thread 1: 33.06 h/s
08:58:11 | Total: 68.95 h/s - Max: 69.42 h/s
08:58:14 | Stop signal received, Quitting...
08:58:14 | Large Page Scratchpad 4MB Buffer 0x7f92b8600000 released.
08:58:14 | Large Page Scratchpad 4MB Buffer 0x7f92b9400000 released.
08:58:14 | Pool connection socket closed.
08:58:14 | Mining thread 0 stopped.
08:58:14 | Mining thread 1 stopped.
08:58:14 | Shared Large Page 0x7f92b9800000 released.


and xmrstak:

[2019-02-07 08:59:02] : Mining coin: monero
[2019-02-07 08:59:02] : Starting 1x thread, affinity: 0.
[2019-02-07 08:59:02] : hwloc: memory pinned
[2019-02-07 08:59:02] : Starting 1x thread, affinity: 1.
[2019-02-07 08:59:02] : hwloc: memory pinned
[2019-02-07 08:59:02] : Starting 1x thread, affinity: 2.
[2019-02-07 08:59:02] : hwloc: memory pinned
[2019-02-07 08:59:02] : Fast-connecting to pool.supportxmr.com:5555 pool ...
[2019-02-07 08:59:02] : Pool pool.supportxmr.com:5555 connected. Logging in...
[2019-02-07 08:59:02] : Difficulty changed. Now: 10000.
[2019-02-07 08:59:02] : Pool logged in.
[2019-02-07 08:59:02] : Switch to assembler version for 'intel_avx' cpu's
[2019-02-07 08:59:02] : Switch to assembler version for 'intel_avx' cpu's
[2019-02-07 08:59:02] : Switch to assembler version for 'intel_avx' cpu's
HASHRATE REPORT - CPU
| ID |    10s |    60s |    15m | ID |    10s |    60s |    15m |
|  0 |   39.1 |   (na) |   (na) |  1 |   27.2 |   (na) |   (na) |
|  2 |   39.9 |   (na) |   (na) |
Totals (CPU):   106.3    0.0    0.0 H/s
-----------------------------------------------------------------
Totals (ALL):    106.3    0.0    0.0 H/s
Highest:     0.0 H/s
-----------------------------------------------------------------
HASHRATE REPORT - CPU
| ID |    10s |    60s |    15m | ID |    10s |    60s |    15m |
|  0 |   42.6 |   (na) |   (na) |  1 |   26.1 |   (na) |   (na) |
|  2 |   40.2 |   (na) |   (na) |
Totals (CPU):   109.0    0.0    0.0 H/s
-----------------------------------------------------------------
Totals (ALL):    109.0    0.0    0.0 H/s
Highest:   107.5 H/s
-----------------------------------------------------------------
[2019-02-07 08:59:46] : Difficulty changed. Now: 8108.
[2019-02-07 08:59:46] : New block detected.
HASHRATE REPORT - CPU
| ID |    10s |    60s |    15m | ID |    10s |    60s |    15m |
|  0 |   38.5 |   40.6 |   (na) |  1 |   28.6 |   27.3 |   (na) |
|  2 |   39.0 |   39.1 |   (na) |
Totals (CPU):   106.2  107.1    0.0 H/s
-----------------------------------------------------------------
Totals (ALL):    106.2  107.1    0.0 H/s
Highest:   109.2 H/s
-----------------------------------------------------------------
[2019-02-07 09:00:46] : Difficulty changed. Now: 5405.
[2019-02-07 09:00:46] : New block detected.
[2019-02-07 09:00:51] : Result accepted by the pool.
[2019-02-07 09:01:39] : New block detected.
[2019-02-07 09:01:46] : Difficulty changed. Now: 5000.
[2019-02-07 09:01:46] : New block detected.
[2019-02-07 09:02:46] : New block detected.
[2019-02-07 09:03:00] : New block detected.
HASHRATE REPORT - CPU
| ID |    10s |    60s |    15m | ID |    10s |    60s |    15m |
|  0 |   45.6 |   42.6 |   (na) |  1 |   25.4 |   26.0 |   (na) |
|  2 |   36.7 |   36.9 |   (na) |
Totals (CPU):   107.9  105.6    0.0 H/s
-----------------------------------------------------------------
Totals (ALL):    107.9  105.6    0.0 H/s
Highest:   109.2 H/s
-----------------------------------------------------------------
[2019-02-07 09:03:46] : New block detected.

add --legacy to force low cpu usage. otherwise the cpu gets involved to sync the gpu and on a weak cpu, it may be heavy. depending on the rig it may be better or worse. looks like on yours it's worse, so use legacy mode.

you shouldn't delete --no-cpu option if you wanna your cpu to take rest ))

Hi, why this miner(gpu mine) don't work on lower cpu very well? on intel q4400 4gb ram 9-gpu(6-rx 580-8gb,3-rx 480-8gb) the cpu is --no-cpu is delete on config and is 100% usage why? on srbminer is working fine low cpu usage

 The GPU configuration:
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":1680 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":1680 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":1680 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":1680 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 2, "multi_hash":1680 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 2, "multi_hash":1680 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 3, "multi_hash":1680 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 3, "multi_hash":1680 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 4, "multi_hash":1680 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 4, "multi_hash":1680 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 5, "multi_hash":1680 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 5, "multi_hash":1680 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 6, "multi_hash":1680 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 6, "multi_hash":1680 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 7, "multi_hash":1680 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 7, "multi_hash":1680 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 8, "multi_hash":1680 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 8, "multi_hash":1680 },

hi, Pool-managed Autoswitch not work in Gpu version ?