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

How to restart miner if hashrate lower than specific number

@JCE-Miner: Sorry for not responding immediately, and thanks for the quick response and improvements!
--mport - checked at the very beginning (033j).
--mpsw - unfortunately not working.
  Memories of Clamore (Standalone utility "EthMan").
1. Monitoring: online / offline
2. Process control: start / stop
3. Configuration editing: 1 core or 16, change pool.
- without having to go to the PC by the ip address or physically.
I hope that someday I will be able to remotely control, as before

Hello,

I'm adding on to the "Segmentation fault (core dumped)" conversation . I am running release "m" on two Linux boxes and the miner periodically crashes on both systems. Sometimes they run for a large number of hours and sometimes they fail quickly. So far I have not made it past 24 hours on either system without re-starting the miners. Here are the specs for each box:


System One
Z87-GD65 GAMING (MS-7845)                         - motherboard
Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz   - processor
32GiB                                                                 - memory
Ubuntu 18.04.1 LTS                                           - OS

System Two
ASRock 970 Extreme4                                      - motherboard
AMD FX-8320E Eight-Core Processor              - processor
12GiB                                                                 - memory
Ubuntu 18.10                                                     - OS

An additional comment is that I experienced the same core dumps with the prior JCE release. I wanted to add this information for you because the problem seems to be more general in nature given that it is happening across different distros and hardware configs. My final observation is that I am running the miner on two WIN-10 boxes and I have had a couple of segmentation faults on them as well although they are running mostly with out issue.

Hope this helps a bit!

Stellite: right i release the GPU version now.

cpu perf: i did a lot of tests to compare 2 separate JCE instances against mixed mining, and found a way to slightly improve the efficiency, but my result were inconsistent since the cpu perf is very sensible to any external usage. So try the new version, with your 2 cpu threads plus GPUs and things should be like +1% better pool side. I hope.
I don't count it as a bug, but yes it lacked some optimizations.

0.33b16 GPU

Thanks for the detailed explanation.  I've let my larger rig run about a week now, and it's stabilized at a ~3% spread, which is once again almost exactly the CPU h/r (pool is showing a 24hr of 9.8kh/s atm.)


I wasn't really comparing yours to other miners - I already know yours is the best.  But the part that doesn't align w/ your explanation (and why i suggested there may be a bug) is that this discrepancy goes away when the gpu and cpu are split into independent processes.  Really not a big deal at all - i'm fine splitting them, just thought i'd give you a heads up in case it was something that could be fixed.

for V8 better -t 2 - 104 h/s
for turtles perfect -t 4 - 420 h/s 
This new CPU 200GE is a kind of RX550 (minimum price 55$ and minimum power consumption - tdp 35W)

STELLITE ANNOUNCEMENT, https://medium.com/stellitecash/fork-announcement-stellite-v5-63cc481a880a ."As fork height we decided the block 503001 and it should happen approximately 16/1/2019 1am UTC."

Large pages: they are used the same way as day one, and enabled automatically by default, when possible, so when run as admin (at least once) on a Windows 10 and/or pro. otherwise (win 7/8) manual config is needed.

windows may run out of pages after some time, while it's more rare on linux. quick fix: reboot.

webchain, hycon: i answered just above. my top priority remains masari. any test pool somewhere?

let me look at that ryzen for best config. i've a r5 but no r3

Edit: try
--auto -t 2
and
--auto -t 4

one should be the optimal, i bet on 1st one

Collected a rig with the new Athlon 200GE processor - 2 cores / 4 threads , 4M cache (its core is from Ryzen 3, with two cores disabled). What are the correct settings V8 for this CPU?

JCE, Masari fork announced: "We're preparing for a v0.3.0.0 protocol upgrade (code name Dandy Dromedary) coming in ~14 days, set for block #363,000 which will introduce SECOR (uncle mining), CNFastv2 PoW variant, and multi-output Bulletproofs (https://github.com/masari-project/masari/releases/tag/v0.3.0.0 )"

Hello JCE!
I got issue with FX 8350. Got 2 fx8350 in different MB. One doing fine with this config

"cpu_threads_conf" :
[
     { "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 },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 4, "use_cache" : true },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 5, "use_cache" : true },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 6, "use_cache" : true },
     { "cpu_architecture" : "auto", "affine_to_cpu" : 7, "use_cache" : true },
]

 But second one gives me error "Failed to allocate 2MB Large Page Scratchpad Buffer, using normal memory (slower)."
Same configs. Same UPlexa coin. Only difference is failed system have 4G ram and OK system got 16G ram. Is it a case or something else? Large pages are unlocked for both systems. Hashrate at monero v8 a same(~350H/s).

 Here is a log.

              +--------------------------------------+
              | JC Expert Cryptonote CPU Miner 0.33n |
              +--------------------------------------+


For Windows 64-bits
Analyzing Processors topology...
AMD FX(tm)-8350 Eight-Core Processor
Assembly codename: bulldozer
  SSE2    : Yes
  SSE3    : Yes
  SSE4    : Yes
  AES     : Yes
  AVX     : Yes
  AVX2    : No

Found CPU 0, with:
  L1 Cache:    16 KB
  L2 Cache:  2048 KB, shared with CPU 1
  L3 Cache:  8192 KB, shared with CPU 1, 2, 3, 4, 5, 6, 7
Found CPU 1, with:
  L1 Cache:    16 KB
  L2 Cache:  2048 KB, shared with CPU 0
  L3 Cache:  8192 KB, shared with CPU 0, 2, 3, 4, 5, 6, 7
Found CPU 2, with:
  L1 Cache:    16 KB
  L2 Cache:  2048 KB, shared with CPU 3
  L3 Cache:  8192 KB, shared with CPU 0, 1, 3, 4, 5, 6, 7
Found CPU 3, with:
  L1 Cache:    16 KB
  L2 Cache:  2048 KB, shared with CPU 2
  L3 Cache:  8192 KB, shared with CPU 0, 1, 2, 4, 5, 6, 7
Found CPU 4, with:
  L1 Cache:    16 KB
  L2 Cache:  2048 KB, shared with CPU 5
  L3 Cache:  8192 KB, shared with CPU 0, 1, 2, 3, 5, 6, 7
Found CPU 5, with:
  L1 Cache:    16 KB
  L2 Cache:  2048 KB, shared with CPU 4
  L3 Cache:  8192 KB, shared with CPU 0, 1, 2, 3, 4, 6, 7
Found CPU 6, with:
  L1 Cache:    16 KB
  L2 Cache:  2048 KB, shared with CPU 7
  L3 Cache:  8192 KB, shared with CPU 0, 1, 2, 3, 4, 5, 7
Found CPU 7, with:
  L1 Cache:    16 KB
  L2 Cache:  2048 KB, shared with CPU 6
  L3 Cache:  8192 KB, shared with CPU 0, 1, 2, 3, 4, 5, 6

Preparing 7 Mining Threads...

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

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

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

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

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

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

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

Cryptonight Variation: Cryptolight-uPlexa fork of Dec-2018

Low intensity.

Starting CPU Thread 0, affinity: CPU 1
Thread 0 successfully bound to CPU 1
Allocated shared Large Page at: 00000225f2a00000
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 1 of NUMA node 0 at: 00000225f2c00000

Starting CPU Thread 1, affinity: CPU 2
Thread 1 successfully bound to CPU 2
Reuse part of 2MB Cached Large Page Scratchpad Buffer at: 00000225f2d00000

Starting CPU Thread 2, affinity: CPU 3
Thread 2 successfully bound to CPU 3
Failed to allocate 2MB Large Page Scratchpad Buffer, using normal memory (slower).

Starting CPU Thread 3, affinity: CPU 4
Thread 3 successfully bound to CPU 4
Failed to allocate 2MB Large Page Scratchpad Buffer, using normal memory (slower).

Starting CPU Thread 4, affinity: CPU 5
Thread 4 successfully bound to CPU 5
Failed to allocate 2MB Large Page Scratchpad Buffer, using normal memory (slower).

Starting CPU Thread 5, affinity: CPU 6
Thread 5 successfully bound to CPU 6
Failed to allocate 2MB Large Page Scratchpad Buffer, using normal memory (slower).

Starting CPU Thread 6, affinity: CPU 7
Thread 6 successfully bound to CPU 7
Failed to allocate 2MB Large Page Scratchpad Buffer, using normal memory (slower).
Devfee for CPU is 1.5%

04:07:27 | Uplexa (UPX) Mining session starts!

Hi JCE,

This work with webchain and hycon?

Thanks

As with my query above (#2261) large pages is manually activated.
I'm hoping you can help me with this.

Thanks in advance,

JCE miner can't enable large pages if they disabled? Maybe you add this option in miner to auto-enable them like Claymore?

P4 32 bits crash on Linux: I'll redo a test on my Core2 duo, the oldest CPU i have, but not sure at all i can reproduce the bug
Sad it would have shined since old cpu mining is my niche expertise, but maybe you use some old Linux distrib or something. It's a lot harder to support linux well because of the large variety of distribs. And i'm also more a Windows person.

Large pages, see the doc here, it needs to be manually enabled, but that's the exact same as for any other miner, so if you find a guide for xmrstak/xmrig/whatever, it will work the same.
https://github.com/jceminer/cn_cpu_miner#large-pages

This can accure if you system have small amount of RAM or running too long from boot. Try to reboot and launch again.

Hi  I tried running JCE miner on Ubuntu 16.04 on an old 32bit dual cpu server to CPU mine Uplexa.
I have compiled the miner with my details but when i start the miner with ./start.sh i get the following:

miner@Miner:/jce_cn_cpu_miner.linux.033m$ ./start.sh

              +--------------------------------------+
              | JC Expert Cryptonote CPU Miner 0.33m |
              +--------------------------------------+


For Linux 32-bits
Analyzing Processors topology...
Dual Intel(R) Xeon(TM) CPU 3.06GHz
Assembly codename: pentium4
  SSE2    : Yes
  SSE3    : No
  SSE4    : No
  AES     : No
  AVX     : No
  AVX2    : No

Auto-configuration, selected CPUs will be highlighted...
Segmentation fault (core dumped)
miner@Miner:/jce_cn_cpu_miner.linux.033m$

Can someone please shed some light on this issue and guide me to fixing it?
 P.S I no Linux expert but with guidance can find my way through.

Thanks in advance for any help given.

Processor AMD Ryzen3 2200G
Why?

I thought so, I was hoping for the solution as with ETH it was previously case to have huge swap, but it was later eliminated.

online is 0.33n CPU Windows