Hi doktor83,
I am doing a lot of tests on CPU mining with RandomX algo.
I am using version 0.1.6 on a Fujitsu Primergy RX2560 M1 server.
I have two Intel XEON E5-2630 V3 @ 2.40GHZ 16 cores, 32 threads available
I am doing a lot of tests on CPU mining with RandomX algo.
I am using version 0.1.6 on a Fujitsu Primergy RX2560 M1 server.
I have two Intel XEON E5-2630 V3 @ 2.40GHZ 16 cores, 32 threads available
Hi, try 0.1.7 because it should better allocate threads, and let's talk then
Some hash rates. I've got an i9-7980XE @~3.6ghz
M7Mv2:
SRB: 18 threads ~272 kh/s, ~72% cpu usage, ~50mb RAM
Minerd (Wolf's): 18 threads ~340 kh/s, ~66% cpu usage, ~4mb RAM
M7Mv2:
SRB: 18 threads ~272 kh/s, ~72% cpu usage, ~50mb RAM
Minerd (Wolf's): 18 threads ~340 kh/s, ~66% cpu usage, ~4mb RAM
What is the hashrate for 1 thread on both miners, can you test that?
Testing RandomX.
1 thread or 12 threads, same message. What does that means ?
[2019-11-18 15:40:02] Insufficient system resources available to allocate 2129920 kB in large-page memory
[2019-11-18 15:40:06] Dataset & Cache & VM initialized in 5014 ms
1 thread or 12 threads, same message. What does that means ?
[2019-11-18 15:40:02] Insufficient system resources available to allocate 2129920 kB in large-page memory
[2019-11-18 15:40:06] Dataset & Cache & VM initialized in 5014 ms
It means there are not enough free pages, i put a small text on first post + readme:
Quote
If you get "Insufficient system resources available to allocate X kB in large-page memory" message, that means you dont have enough FREE memory left, a computer restart should solve this.
Large-page memory regions may be difficult to obtain after the system has been running for a long time because the physical space for each large page must be contiguous, but the memory may have become fragmented.
If you still get this message even after restarting, try increasing virtual memory.
Large-page memory regions may be difficult to obtain after the system has been running for a long time because the physical space for each large page must be contiguous, but the memory may have become fragmented.
If you still get this message even after restarting, try increasing virtual memory.
Xmrig displays this differently ( ' ..huge pages 75% 3/4.. ' ), but its probably not so scarry because users probably don't notice that
