SRBMiner-MULTI AMD & NVIDIA & INTEL & CPU miner

[doktor83]

Still need to improve the auto selection of best config for randomx 

[1714002367]

1714002367

[1714002367]

1714002367

[KolordZ]

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 !

[doktor83]

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.

[doktor83]

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

[dragonmike]

Any hashrate indics for k12 on commonly used GPUs?

[doktor83]

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

[dragonmike]

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...

[KolordZ]

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

Nico

[WhyMe]

And what if you run 15 threads, with HT ?
For me 1.6x more speed is 60% more speed, not the case here, no ?

[IncludeBeer]

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

[WhyMe]

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

[doktor83]

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

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:

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 

[WhyMe]

No other option than restart ? It's my server

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

Very low result compared with KolordZ

[doktor83]

No other option than restart ? It's my server

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

Very low result compared with KolordZ

You can get 50+% more hashrate if using large pages

You tried --cpu-threads 12 --cpu-affinity 0xAAAAAA ?

[WhyMe]

With your mask, gives 1693H/s on 5mn avg

[KolordZ]

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

Hello @doktor83,

Some news with SRBMiner-MULTI 0.1.7 :

I use 2x Intel XEON E5-2630 V3 @ 2.40GHZ
16 cores, 32 threads available with Hyper-Threading

WITH Hyper-Threading option enabled :

https://zupimages.net/up/19/47/vmyq.png

- Only 50-55% processor activity
- Only 16 Threads used out of 32
- Around 4400Hr/s
- Can't get more with cpu-affinity and cpu-threads

WITHOUT Hyper-Threading option enabled :

https://zupimages.net/up/19/47/z2xe.png

- 100% processor activity
- 16 Threads used out of 16
- Around 4400Hr/s (less than previous version of SRBMiner MULTI 0.1.6 : 4900Hr/s)

-> Previous version used only 15 threads out of 16 in auto-config compare to 0.1.7

I use auto-config each time for doing tests

Nico

[doktor83]

Hello @doktor83,

Some news with SRBMiner-MULTI 0.1.7 :

I use 2x Intel XEON E5-2630 V3 @ 2.40GHZ
16 cores, 32 threads available with Hyper-Threading

WITH Hyper-Threading option enabled :

https://zupimages.net/up/19/47/vmyq.png

- Only 50-55% processor activity
- Only 16 Threads used out of 32
- Around 4400Hr/s
- Can't get more with cpu-affinity and cpu-threads

WITHOUT Hyper-Threading option enabled :

https://zupimages.net/up/19/47/z2xe.png

- 100% processor activity
- 16 Threads used out of 16
- Around 4400Hr/s (less than previous version of SRBMiner MULTI 0.1.6 : 4900Hr/s)

-> Previous version used only 15 threads out of 16 in auto-config compare to 0.1.7

I use auto-config each time for doing tests

Nico

It is hard, or maybe not even  possible at all to make the auto config work good on every system with different cpu combinations.
Ver 0.1.7 does the threads & affinity calculation in auto mode based on available L3 cache sizes, where 0.1.6 was not . The logic used there was really poor 

So you can set --cpu-threads 15 by hand, without affinity set at all with the HT off, and should get the 4900h/s again.

[SamaelDNM]

very well, something like that was what I was looking for, what I see is an all-in-one, so I see it very sophisticated  

[KolordZ]

It is hard, or maybe not even  possible at all to make the auto config work good on every system with different cpu combinations.
Ver 0.1.7 does the threads & affinity calculation in auto mode based on available L3 cache sizes, where 0.1.6 was not . The logic used there was really poor  

So you can set --cpu-threads 15 by hand, without affinity set at all with the HT off, and should get the 4900h/s again.

Yes, I could probably use --cpu-threads 15 without Hyper-Threading enabled to get the 4900h/s again, but this is not that I would like to know.

I would like to know how can we use the Hyper-Threading to get a better hashrate.

If we can get 4400h/s with H-T (Hyper-Threading) enabled and only 55% processor activity with 16 thread out of 32 we could probably get like 30 or 31 threads out of 32 and get like, 7000h/s (x1.6)

EDIT : with --cpu-threads 15 without H-T I have 4900h/s again

Nico

[doktor83]

It is hard, or maybe not even  possible at all to make the auto config work good on every system with different cpu combinations.
Ver 0.1.7 does the threads & affinity calculation in auto mode based on available L3 cache sizes, where 0.1.6 was not . The logic used there was really poor  

So you can set --cpu-threads 15 by hand, without affinity set at all with the HT off, and should get the 4900h/s again.

Yes, I could probably use --cpu-threads 15 without Hyper-Threading enabled to get the 4900h/s again, but this is not that I would like to know.

I would like to know how can we use the Hyper-Threading to get a better hashrate.

If we can get 4400h/s with H-T (Hyper-Threading) enabled and only 55% processor activity with 16 thread out of 32 we could probably get like 30 or 31 threads out of 32 and get like, 7000h/s (x1.6)

EDIT : with --cpu-threads 15 without H-T I have 4900h/s again

Nico

No because you are limited with the size of L3 and L2 caches.

But you can run Arqma on 32 threads probably