Pages:
Author

Topic: SRBMiner-MULTI GPU & CPU Miner 0.9.4 - page 53. (Read 42480 times)

sr. member
Activity: 661
Merit: 250
November 19, 2019, 09:23:41 AM
#93
No other option than restart ? It's my server Cheesy

EDIT

Result on my server ( without restart, so always with the ressource warning ) :

CPU0: Intel(R) Xeon(R) CPU E5645 @ 2.40GHz [L3:12288 KB][L2:256 KB][L1:32 KB]
CPU1: Intel(R) Xeon(R) CPU E5645 @ 2.40GHz [L3:12288 KB][L2:256 KB][L1:32 KB]

With default settings ( using 12 threads ) :
1mn avg = 1636H/s
5mn avg = 1653H/s

Tried playing with --cpu-threads and --cpu-affinity, but no better result than with default settings Cheesy

Very low result compared with KolordZ Sad
hero member
Activity: 2520
Merit: 626
November 18, 2019, 05:21:14 PM
#92
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

Hi, try 0.1.7 because it should better allocate threads, and let's talk then Smiley

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

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

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.


Xmrig displays this differently ( ' ..huge pages 75% 3/4.. ' ), but its probably not so scarry because users probably don't notice that  Cool
sr. member
Activity: 661
Merit: 250
November 18, 2019, 04:43:08 PM
#91
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
legendary
Activity: 1164
Merit: 1010
November 18, 2019, 04:37:51 PM
#90
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
sr. member
Activity: 661
Merit: 250
November 18, 2019, 04:23:11 PM
#89
And what if you run 15 threads, with HT ?
For me 1.6x more speed is 60% more speed, not the case here, no ?
newbie
Activity: 28
Merit: 0
November 18, 2019, 02:42:47 PM
#88
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 would like to share my results with you and discuss about hyper-threading option.

1st test (WITH hyper-threading option enabled in BIOS, default option) :

- 16 cores, 32 threads available
SRB uses only 16 threads with auto config with a speed of 4400 Hr / s

1 in 2 thread is not used when analyzing processors activity.
I tried to play with the CPU Affinity and CPU Thread options but could not get better than 4400. If I force 32 threads (or 24, or 30) with the CPU threads option I get a ridiculous speed .

2nd test (WITHOUT hyper-threading option activated in the BIOS) :

- 16 cores, 16 threads available.
SRB uses 15 threads in auto setup. The speed increases a bit, 4900Hr / s

So I would like to know if you knew about it and if you intended to add in your code the hyper threading. If you do not plan to work on it maybe you could warn people not to use the hyper threading option to have a better Hr / S.
I think if hyper-threading option can be manage in SRB we can get maybe 1.6x more speed, what do you think ?

Thank you for your feedback on the subject Smiley

Nico
hero member
Activity: 1274
Merit: 556
November 18, 2019, 01:16:05 PM
#87
Any hashrate indics for k12 on commonly used GPUs?

auto intensity settings, memory is not important for K12 i just benchmarked for you :

Rx560 [14 cu] 1170/1500 : ~340MHS
Vega56 [56 cu] 1450/940 : ~1700MHS
Oh dear. That one's gone to the ASICs/FPGAs it seems.
$0.15/day per Vega... Tongue
hero member
Activity: 2520
Merit: 626
November 18, 2019, 12:19:15 PM
#86
Any hashrate indics for k12 on commonly used GPUs?

auto intensity settings, memory is not important for K12 i just benchmarked for you :

Rx560 [14 cu] 1170/1500 : ~340MHS
Vega56 [56 cu] 1450/940 : ~1700MHS
hero member
Activity: 1274
Merit: 556
November 18, 2019, 11:14:27 AM
#85
Any hashrate indics for k12 on commonly used GPUs?
hero member
Activity: 2520
Merit: 626
November 18, 2019, 06:21:43 AM
#84
V0.1.7 beta

+ Added 'm7mv2' algorithm (Magi coin - XMG)
+ Cpu auto configuration should be better than on previous versions
+ Added CPU data to API, also rearranged a few things in API
+ Console window 'Quick Edit' mode disabled on miner start, so users won't accidentally pause miner by clicking in the console window
hero member
Activity: 2520
Merit: 626
November 15, 2019, 03:41:51 PM
#83
Hello @doktor83 !

This is my test... What a poor result as an i7-8750H :/


Code:
[2019-11-13 21:49:19] Startup monitor attached
[2019-11-13 21:49:19] Miner version: 0.1.6
[2019-11-13 21:49:19] Windows version: 10.0 build 18362
[2019-11-13 21:49:20] CPU: Intel(R)Core(TM ) i7-8750H CPU @ 2.20GHz [L3:9216 KB][L2:256 KB][L1:32 KB]
[2019-11-13 21:49:20] Algorithm: randomx
[2019-11-13 21:49:20] Gpu mining: disabled
[2019-11-13 21:49:20] Cpu mining: enabled
[2019-11-13 21:49:20] Huge-pages: enabled
[2019-11-13 21:49:20] HW-Aes: available
[2019-11-13 21:49:20] Startup monitor: enabled
[2019-11-13 21:49:20] Socket init done
[2019-11-13 21:49:20] Starting init of worker threads
[2019-11-13 21:49:20] CPU worker thread 0 bound to PU 0 on node 0
[2019-11-13 21:49:20] CPU worker thread 1 bound to PU 2 on node 0
[2019-11-13 21:49:20] CPU worker thread 2 bound to PU 4 on node 0
[2019-11-13 21:49:20] CPU worker thread 3 bound to PU 6 on node 0
[2019-11-13 21:49:20] CPU worker thread 4 bound to PU 8 on node 0
[2019-11-13 21:49:20] Thread[0] : CPU
[2019-11-13 21:49:20] Thread[1] : CPU
[2019-11-13 21:49:20] Thread[2] : CPU
[2019-11-13 21:49:20] Thread[3] : CPU
[2019-11-13 21:49:20] Thread[4] : CPU
[2019-11-13 21:49:20] Thread[5] : CPU
[2019-11-13 21:49:20] Finished init of worker threads
[2019-11-13 21:49:20] CPU worker thread 5 bound to PU 10 on node 0
[2019-11-13 21:49:20] Startup monitor detached
[2019-11-13 21:49:20] 6 CPU core/s - 12 threads available
[2019-11-13 21:49:20] Using 6 threads for CPU mining
[2019-11-13 21:49:20] Node 0 total memory: 5626 MB
[2019-11-13 21:49:20] CPU extension : SSE4.1 | AES
[2019-11-13 21:49:20] Gpu-watchdog started [triggers after 5 rounds: 150 sec]
[2019-11-13 21:49:20] HTTP API disabled
[2019-11-13 21:49:20] json_send[201]: {"id":1,"jsonrpc": "2.0","method":"login","params":{"login":"4897Wc5pexE25twCvQ1bpyBEyMZCrdeARSFqfYQBtPfSD6FZrCW6L6zfAB6PnhJJdaVi2Q3r1AgcViBPrMoZGqRj6hhKLUC","pass":"x","agent":"SRBMiner-MULTI/0.1.6"}}
[2019-11-13 21:49:20] json_receive[412]: {"id":1,"jsonrpc":"2.0","error":null,"result":{"id":"500772239118811","job":{"seed_hash":"3b901ea2f0f825a5d3cf7bc0a7e0f7faa8d6efc157c36256b3cc3398f3ee89c7","height":1341994,"blob":"0c0cf4d6b1ee05a4adb049ba70b7cc094b3e07b13933374c8bae270a141b22768c64b5f9ee605100000000dcaf44f9d65426de835141c45f46f13c10b6ed26e385467f9b6f435b34dbb72501","job_id":"899071441393928","target":"b2df0000","algo":"rx/0"},"status":"OK"}}
[2019-11-13 21:49:20] Connected to rx.minexmr.com:4444
[2019-11-13 21:49:20] Initialising dataset & cache & vm
[2019-11-13 21:49:21] memory_manager: Allocated memory with huge page support [2129920 kB]
[2019-11-13 21:49:21] memory_manager: Allocated memory with huge page support [262144 kB]
[2019-11-13 21:49:26] Dataset & Cache & VM initialized in 5649 ms
[2019-11-13 21:49:26] Worker thread 0 allocated L3 scratchpad [HP]
[2019-11-13 21:49:26] Created VM for worker thread 0
[2019-11-13 21:49:26] Worker thread 1 allocated L3 scratchpad [HP]
[2019-11-13 21:49:26] Created VM for worker thread 1
[2019-11-13 21:49:26] Worker thread 2 allocated L3 scratchpad [HP]
[2019-11-13 21:49:26] Created VM for worker thread 2
[2019-11-13 21:49:26] Worker thread 3 allocated L3 scratchpad [HP]
[2019-11-13 21:49:26] Created VM for worker thread 3
[2019-11-13 21:49:26] Worker thread 4 allocated L3 scratchpad [HP]
[2019-11-13 21:49:26] Created VM for worker thread 4
[2019-11-13 21:49:26] Worker thread 5 allocated L3 scratchpad [HP]
[2019-11-13 21:49:26] Created VM for worker thread 5
[2019-11-13 21:49:26] New job received, block height 1341994
[2019-11-13 21:49:58] hashrate: CPU: 995.50 H/s
[2019-11-13 21:49:58] hashrate: Total: 995.50 H/s

I used your guided-setup", SRBMiner MULTI 0.1.6

I missed something ?

Thx for what you've done !

Hi, you could manually set the number of threads and the affinity, maybe it can get out more hash.
New version in a few days, it should have a better auto setup.
newbie
Activity: 28
Merit: 0
November 13, 2019, 05:00:24 PM
#82
Hello @doktor83 !

This is my test... What a poor result as an i7-8750H :/


Code:
[2019-11-13 21:49:19] Startup monitor attached
[2019-11-13 21:49:19] Miner version: 0.1.6
[2019-11-13 21:49:19] Windows version: 10.0 build 18362
[2019-11-13 21:49:20] CPU: Intel(R)Core(TM ) i7-8750H CPU @ 2.20GHz [L3:9216 KB][L2:256 KB][L1:32 KB]
[2019-11-13 21:49:20] Algorithm: randomx
[2019-11-13 21:49:20] Gpu mining: disabled
[2019-11-13 21:49:20] Cpu mining: enabled
[2019-11-13 21:49:20] Huge-pages: enabled
[2019-11-13 21:49:20] HW-Aes: available
[2019-11-13 21:49:20] Startup monitor: enabled
[2019-11-13 21:49:20] Socket init done
[2019-11-13 21:49:20] Starting init of worker threads
[2019-11-13 21:49:20] CPU worker thread 0 bound to PU 0 on node 0
[2019-11-13 21:49:20] CPU worker thread 1 bound to PU 2 on node 0
[2019-11-13 21:49:20] CPU worker thread 2 bound to PU 4 on node 0
[2019-11-13 21:49:20] CPU worker thread 3 bound to PU 6 on node 0
[2019-11-13 21:49:20] CPU worker thread 4 bound to PU 8 on node 0
[2019-11-13 21:49:20] Thread[0] : CPU
[2019-11-13 21:49:20] Thread[1] : CPU
[2019-11-13 21:49:20] Thread[2] : CPU
[2019-11-13 21:49:20] Thread[3] : CPU
[2019-11-13 21:49:20] Thread[4] : CPU
[2019-11-13 21:49:20] Thread[5] : CPU
[2019-11-13 21:49:20] Finished init of worker threads
[2019-11-13 21:49:20] CPU worker thread 5 bound to PU 10 on node 0
[2019-11-13 21:49:20] Startup monitor detached
[2019-11-13 21:49:20] 6 CPU core/s - 12 threads available
[2019-11-13 21:49:20] Using 6 threads for CPU mining
[2019-11-13 21:49:20] Node 0 total memory: 5626 MB
[2019-11-13 21:49:20] CPU extension : SSE4.1 | AES
[2019-11-13 21:49:20] Gpu-watchdog started [triggers after 5 rounds: 150 sec]
[2019-11-13 21:49:20] HTTP API disabled
[2019-11-13 21:49:20] json_send[201]: {"id":1,"jsonrpc": "2.0","method":"login","params":{"login":"4897Wc5pexE25twCvQ1bpyBEyMZCrdeARSFqfYQBtPfSD6FZrCW6L6zfAB6PnhJJdaVi2Q3r1AgcViBPrMoZGqRj6hhKLUC","pass":"x","agent":"SRBMiner-MULTI/0.1.6"}}
[2019-11-13 21:49:20] json_receive[412]: {"id":1,"jsonrpc":"2.0","error":null,"result":{"id":"500772239118811","job":{"seed_hash":"3b901ea2f0f825a5d3cf7bc0a7e0f7faa8d6efc157c36256b3cc3398f3ee89c7","height":1341994,"blob":"0c0cf4d6b1ee05a4adb049ba70b7cc094b3e07b13933374c8bae270a141b22768c64b5f9ee605100000000dcaf44f9d65426de835141c45f46f13c10b6ed26e385467f9b6f435b34dbb72501","job_id":"899071441393928","target":"b2df0000","algo":"rx/0"},"status":"OK"}}
[2019-11-13 21:49:20] Connected to rx.minexmr.com:4444
[2019-11-13 21:49:20] Initialising dataset & cache & vm
[2019-11-13 21:49:21] memory_manager: Allocated memory with huge page support [2129920 kB]
[2019-11-13 21:49:21] memory_manager: Allocated memory with huge page support [262144 kB]
[2019-11-13 21:49:26] Dataset & Cache & VM initialized in 5649 ms
[2019-11-13 21:49:26] Worker thread 0 allocated L3 scratchpad [HP]
[2019-11-13 21:49:26] Created VM for worker thread 0
[2019-11-13 21:49:26] Worker thread 1 allocated L3 scratchpad [HP]
[2019-11-13 21:49:26] Created VM for worker thread 1
[2019-11-13 21:49:26] Worker thread 2 allocated L3 scratchpad [HP]
[2019-11-13 21:49:26] Created VM for worker thread 2
[2019-11-13 21:49:26] Worker thread 3 allocated L3 scratchpad [HP]
[2019-11-13 21:49:26] Created VM for worker thread 3
[2019-11-13 21:49:26] Worker thread 4 allocated L3 scratchpad [HP]
[2019-11-13 21:49:26] Created VM for worker thread 4
[2019-11-13 21:49:26] Worker thread 5 allocated L3 scratchpad [HP]
[2019-11-13 21:49:26] Created VM for worker thread 5
[2019-11-13 21:49:26] New job received, block height 1341994
[2019-11-13 21:49:58] hashrate: CPU: 995.50 H/s
[2019-11-13 21:49:58] hashrate: Total: 995.50 H/s

I used your guided-setup", SRBMiner MULTI 0.1.6

I missed something ?

Thx for what you've done !
hero member
Activity: 2520
Merit: 626
November 13, 2019, 06:11:00 AM
#81
Still need to improve the auto selection of best config for randomx  Angry
hero member
Activity: 1274
Merit: 556
November 12, 2019, 06:03:53 PM
#80
RX Vega 56@64, core clk @ 1500mhz

CKB: ~ 673 MH/s
hero member
Activity: 2520
Merit: 626
November 12, 2019, 03:19:30 PM
#79
This thread lacks highly important hashrate reports!...

Come on fellas, share your findings.

i5-2500K CPU @ 3.30GHz @ 3 threads

RandomX: ~ 1490 h/s
RandomXL: ~ 1520 h/s
RandomWow: ~ 1815 h/s
RandomArq: ~ 7620 h/s

Celeron(R) CPU  J1800  @ 2.41GHz @ 1 thread  Grin

RandomXL: ~ 63 h/s
RandomWow: ~ 88 h/s
hero member
Activity: 2520
Merit: 626
November 12, 2019, 12:17:44 PM
#78
I fixed & re-uploaded, download again from github please :

https://github.com/doktor83/SRBMiner-Multi/releases/tag/0.1.6

if you set the number of threads yourself, you should also set the coresponding affinity.
hero member
Activity: 2520
Merit: 626
November 12, 2019, 11:32:33 AM
#77
After the add ---cpu-affinity 0x00003FFFFFFFFFFF  closes with such an error

terminate called after throwing an instance of 'std::out_of_range'
  what():  stoul
SEGFAULT ?

Shutting down miner...

Delete ---cpu-affinity 0x00003FFFFFFFFFFF, works on 24 threads


Ouch, you found a bug, thanks Smiley
hero member
Activity: 1274
Merit: 556
November 12, 2019, 11:03:58 AM
#76
This thread lacks highly important hashrate reports!...

Come on fellas, share your findings.
hero member
Activity: 2520
Merit: 626
November 12, 2019, 10:59:53 AM
#75

Hello
Yes it's better but I have x4 Opteron 6234 48 threads.
When I load on 46 threads it can load only 24, I can use the utility to load on 46 but it should be done manually, or 2 miners on 24 threads.

[2019-11-12 16:56:18] OpenCL not found, gpu mining disabled
[2019-11-12 16:56:18] Startup monitor attached
[2019-11-12 16:56:18] Miner version: 0.1.6
[2019-11-12 16:56:18] Windows version: 10.0 build 17763
[2019-11-12 16:56:18] NUMA binding: enabled
[2019-11-12 16:56:18] CPU x 4: AMDOpteron(TM) Processor 6234                  [L3:6144 KB][L2:2048 KB][L1:16 KB]
[2019-11-12 16:56:18] Algorithm: randomarq
[2019-11-12 16:56:18] Gpu mining: disabled
[2019-11-12 16:56:18] Cpu mining: enabled
[2019-11-12 16:56:18] Huge-pages: enabled
[2019-11-12 16:56:18] HW-Aes: available
[2019-11-12 16:56:18] Startup monitor: enabled
[2019-11-12 16:56:18] Starting init of worker threads
[2019-11-12 16:56:18] Finished init of worker threads
[2019-11-12 16:56:19] Startup monitor detached
[2019-11-12 16:56:19] 24 CPU core/s - 48 threads available
[2019-11-12 16:56:19] Using 46 threads for CPU mining
[2019-11-12 16:56:19] CPU extension : SSE4.1 | AES
[2019-11-12 16:56:19] Gpu-watchdog started [triggers after 5 rounds: 150 sec]
[2019-11-12 16:56:19] HTTP API disabled
[2019-11-12 16:56:19] Connected to arqma.herominers.com:10641
[2019-11-12 16:56:19] Initialising datasets & caches & vms
[2019-11-12 16:56:34] miner_result: CPU result 0xa5f5a6b7 accepted [44ms]
[2019-11-12 16:56:37] miner_result: CPU result 0x5cb79005 accepted [45ms]
[2019-11-12 16:56:38] miner_result: CPU result 0x8b5fc8c2 accepted [49ms]
[2019-11-12 16:56:41] miner_result: CPU result 0xac85d39b accepted [43ms]

Notice I'm talking 46 threads, and he's 24 threads.
Thank you

Try adding :

for 48 threads

--cpu-threads 48 --cpu-affinity 0x0000FFFFFFFFFFFF

for 48 threads

--cpu-threads 46 --cpu-affinity 0x00003FFFFFFFFFFF
hero member
Activity: 2520
Merit: 626
November 12, 2019, 08:28:50 AM
#74
V0.1.6 beta

+ Fixed threads binding on systems with more than 1 numa node
+ Better auto configuration for cpu mining
+ Previous two fixes should bring higher hashrates
+ Added pool controlled algorithm switching capability (Monero Ocean)
+ Added pool config parameter "algo_min_time" and --algo-min-time to cli (Monero Ocean)
+ Added pool config parameter "keepalive" and --keepalive to cli
Pages:
Jump to: