SRBMiner-MULTI AMD & NVIDIA & INTEL & CPU miner

[io8621]

You may take a look on Bismuth(SHA-224) 

Yes, Bismuth would be nice.

[1715016048]

1715016048

[1715016048]

1715016048

[1715016048]

1715016048

[1715016048]

1715016048

[mtl1979]

I think there won't be new CN variant algorithms anymore, probably a lot of old/new projects will follow the RandomX path. SRBMiner-CN is working with the existing algorithms, so any project that uses one of those could be mined with SRBMiner-CN.

If there will be any new CN variants though, i will consider adding them to the new MULTI miner. This one is an improved version of the old miner, i fixed a lot of bugs, added cpu mining support etc.

Talleo uses CryptoNight Ultra Variant 2, which is similar to CryptoNight Turtle (CryptoNight Ultra Lite Variant 2 or cn_pico/turtle), but is still incompatible. As latest xmr-stak has issues with rejected shares with both CPU and GPU mining, and xmrig doesn't support the algorithm, people are complaining they can't use SRBMiner-CN with their AMD GPUs.

[doktor83]

If interested in mining Nervos CKB, here's a video tutorial on how to set up SRBMiner :

https://youtu.be/t3Zp9f9TuJY

[EnglishGentleman]

this miner dont support cn algo? in future too?

You mean RandomX algo ?
I will probably add CPU support, GPU not so sure.

Hi. Do you have a planned release date for RandomX please?

[doktor83]

this miner dont support cn algo? in future too?

You mean RandomX algo ?
I will probably add CPU support, GPU not so sure.

Hi. Do you have a planned release date for RandomX please?

Yes, in one or two days

[doktor83]

V0.1.5 beta

+ Added cpu algorithms : RandomX, RandomXL, RandomWow, RandomArq
+ Added cli parameters: --cpu-priority, --disable-huge-pages, --disable-hw-aes, --disable-numa
+ Added pool config parameter 'start_block_height' and --start-block-height cli parameter
+ Fixed a bug that limited the number of threads useable for cpu mining
+ Fixed cpu affinity parameter and thread/s binding to affinity mask
+ Where possible, now using huge pages if available, this should bring a slight performance increase
+ Removed OpenCL dependency if using only cpu miner
+ Added limited Overdrive8 support (adl type 3)

[EnglishGentleman]

V0.1.5 beta

+ Added cpu algorithms : RandomX, RandomXL, RandomWow, RandomArq
+ Added cli parameters: --cpu-priority, --disable-huge-pages, --disable-hw-aes, --disable-numa
+ Added pool config parameter 'start_block_height' and --start-block-height cli parameter
+ Fixed a bug that limited the number of threads useable for cpu mining
+ Fixed cpu affinity parameter and thread/s binding to affinity mask
+ Where possible, now using huge pages if available, this should bring a slight performance increase
+ Removed OpenCL dependency if using only cpu miner
+ Added limited Overdrive8 support (adl type 3)

Hello Doktor


Thanks for the initiative. Single core performance on RandomXL seems good.  However there are some error messages thrown up and multi-core performance is poor at the moment. Can you help?  The test system is Dell R620 server with two Xeon E5-2620 V1 and 28 GBytes of RAM.

First the error messages:

Cannot bind database to node     Cannot bind cache to node    See https://drive.google.com/file/d/1o8AnMtIU3J9WstytBRktOa-L9f_C0BeN/view?usp=sharing

Cannot bind scratchpad to node    See https://drive.google.com/file/d/18G_bTBlkV3hUXC-D9X0sMrui1dSmjkFe/view?usp=sharing


The errors appear if I use the wizard to create the BAT file or make my own BAT file.

How can these errors be fixed please?

The performance issue seems to be that the second CPU is not utilised even though SRBMiner identifies 12 cores and 24 threads.

See pics from HWInfo of the two cores

CPU 0     https://drive.google.com/file/d/1IhRbu9z1F1-DWaJpz7o3dyQvazSOe3VM/view?usp=sharing
CPU 1     https://drive.google.com/file/d/1C2s1PBm9hmzNAv91Jrsk2ZiWGlvW14Va/view?usp=sharing

Here is the command line used   SRBMiner-MULTI.exe --algorithm randomxl  --cpu-threads 0 --pool loki.miner.rocks:5005 --wallet L7f9SMpr43wNERBxCngFyqMoJvkMax8xSitiJY335ra12ucbiEFzgqKfHJg1Q9y58RGMi3TyGvPC94e 6w3zYKK9i9PHmDDr  --cpu-threads

Finally I can't see documentation on how to use CPU affinity  and   --cpu-priority. Please can you add it?

[doktor83]

Hello Doktor


Thanks for the initiative. Single core performance on RandomXL seems good.  However there are some error messages thrown up and multi-core performance is poor at the moment. Can you help?  The test system is Dell R620 server with two Xeon E5-2620 V1 and 28 GBytes of RAM.

First the error messages:

Cannot bind database to node     Cannot bind cache to node    See https://drive.google.com/file/d/1o8AnMtIU3J9WstytBRktOa-L9f_C0BeN/view?usp=sharing

Cannot bind scratchpad to node    See https://drive.google.com/file/d/18G_bTBlkV3hUXC-D9X0sMrui1dSmjkFe/view?usp=sharing


The errors appear if I use the wizard to create the BAT file or make my own BAT file.

How can these errors be fixed please?

The performance issue seems to be that the second CPU is not utilised even though SRBMiner identifies 12 cores and 24 threads.

See pics from HWInfo of the two cores

CPU 0     https://drive.google.com/file/d/1IhRbu9z1F1-DWaJpz7o3dyQvazSOe3VM/view?usp=sharing
CPU 1     https://drive.google.com/file/d/1C2s1PBm9hmzNAv91Jrsk2ZiWGlvW14Va/view?usp=sharing

Here is the command line used   SRBMiner-MULTI.exe --algorithm randomxl  --cpu-threads 0 --pool loki.miner.rocks:5005 --wallet L7f9SMpr43wNERBxCngFyqMoJvkMax8xSitiJY335ra12ucbiEFzgqKfHJg1Q9y58RGMi3TyGvPC94e 6w3zYKK9i9PHmDDr  --cpu-threads

Finally I can't see documentation on how to use CPU affinity  and   --cpu-priority. Please can you add it?

Hi, first try removing the --cpu-threads 0 because that sets the number of threads to 1 

Code:

SRBMiner-MULTI.exe --algorithm randomxl --pool loki.miner.rocks:5005 --wallet L7f9SMpr43wNERBxCngFyqMoJvkMax8xSitiJY335ra12ucbiEFzgqKfHJg1Q9y58RGMi3TyGvPC94e6w3zYKK9i9PHmDDr

You can also try to find the best --cpu-threads by hand for your system.

--cpu-priority is just a number from 1-5, the higher the priority level of a process, the more will be its assigned processor time.
--cpu-affinity is a mask (can be used hex like 0x.... or just the decimal number). An affinity mask is a bit mask indicating what processor(s) a thread or process should be run on by the scheduler of an operating system.

[CjMapope]

V0.1.5 beta

+ Added cpu algorithms : RandomX, RandomXL, RandomWow, RandomArq
+ Added cli parameters: --cpu-priority, --disable-huge-pages, --disable-hw-aes, --disable-numa
+ Added pool config parameter 'start_block_height' and --start-block-height cli parameter
+ Fixed a bug that limited the number of threads useable for cpu mining
+ Fixed cpu affinity parameter and thread/s binding to affinity mask
+ Where possible, now using huge pages if available, this should bring a slight performance increase
+ Removed OpenCL dependency if using only cpu miner
+ Added limited Overdrive8 support (adl type 3)

oh duuude, fuk ya!  going to roll this out to the CPUs and play with it right now, ill report back any issues that arise
im starting to get hyped for RandomX day by day, go'in get me a fancy 3900x, only 700 Beaverdollars, so crazy cheap
Thx for your work

[EnglishGentleman]

Hello Doktor


Thanks for the initiative. Single core performance on RandomXL seems good.  However there are some error messages thrown up and multi-core performance is poor at the moment. Can you help?  The test system is Dell R620 server with two Xeon E5-2620 V1 and 28 GBytes of RAM.

First the error messages:

Cannot bind database to node     Cannot bind cache to node   See https://drive.google.com/file/d/1o8AnMtIU3J9WstytBRktOa-L9f_C0BeN/view?usp=sharing

Cannot bind scratchpad to node    See https://drive.google.com/file/d/18G_bTBlkV3hUXC-D9X0sMrui1dSmjkFe/view?usp=sharing


The errors appear if I use the wizard to create the BAT file or make my own BAT file.

How can these errors be fixed please?

The performance issue seems to be that the second CPU is not utilised even though SRBMiner identifies 12 cores and 24 threads.

See pics from HWInfo of the two cores

CPU 0     https://drive.google.com/file/d/1IhRbu9z1F1-DWaJpz7o3dyQvazSOe3VM/view?usp=sharing
CPU 1     https://drive.google.com/file/d/1C2s1PBm9hmzNAv91Jrsk2ZiWGlvW14Va/view?usp=sharing

Here is the command line used   SRBMiner-MULTI.exe --algorithm randomxl  --cpu-threads 0 --pool loki.miner.rocks:5005 --wallet L7f9SMpr43wNERBxCngFyqMoJvkMax8xSitiJY335ra12ucbiEFzgqKfHJg1Q9y58RGMi3TyGvPC94e 6w3zYKK9i9PHmDDr  --cpu-threads

Finally I can't see documentation on how to use CPU affinity  and   --cpu-priority. Please can you add it?

Hi, first try removing the --cpu-threads 0 because that sets the number of threads to 1  

Code:

SRBMiner-MULTI.exe --algorithm randomxl --pool loki.miner.rocks:5005 --wallet L7f9SMpr43wNERBxCngFyqMoJvkMax8xSitiJY335ra12ucbiEFzgqKfHJg1Q9y58RGMi3TyGvPC94e6w3zYKK9i9PHmDDr

You can also try to find the best --cpu-threads by hand for your system.

--cpu-priority is just a number from 1-5, the higher the priority level of a process, the more will be its assigned processor time.
--cpu-affinity is a mask (can be used hex like 0x.... or just the decimal number). An affinity mask is a bit mask indicating what processor(s) a thread or process should be run on by the scheduler of an operating system.

Hello Doktor

I tried SRMMiner 0.1.5 on a 2 core Celeron machine. It worked first time on the RX.MINEXMR RandomX TestNet. No errors. I followed your instructions for enabling huge pages. That also worked. Performance was 7% higher than XMR-RIG. Great.

Thanks for the feedback about the Dell R620 server.   I started a fresh with your guided-setup.bat and used the RandomX testnet at RX.MINEXMR.

Unfortunately I got exactly the error codes as the first time + the second CPU is not being utilised.

I was able to utilise the second CPU by adding --cpu-affinity 0x555555 . That problem is solved. . Since the miner recognises all the threads and core automatically would it be possible to automatically set the miner up to use all CPUs?

Mining performance of SRBMiner 0-1-5 on RandomX at rx.minexmr.com was initially 92% of the hashrate achieved with XMRIG 4.5.0 Beta but when I ran it overnight hashrate exceeded XMRIG by 5%.  Not bad for your initial release.  I tried adding additional threads but it made no difference. Whereas XMRIG actually goes slower on these CPU when more than 1 thread per core is used.

The Celeron and the Dell R620 run Windows 10 Professional.

How about the binding errors? Do they matter? Perhaps additional performance could be achieved without these errors?

See links below. Thanks in advance for your help.

Screenshots of errors: Cannot bind to XXX errors
https://drive.google.com/file/d/1Mo6NM_wMCjEEB1nyF6Z3OSuPw2XItVFi/view?usp=sharing

https://drive.google.com/file/d/1XnHKjVxDX7qkFwbjIudWVE_0CyJbtUJo/view?usp=sharing

https://drive.google.com/file/d/1pas-ckr-JiVyvtJfA0HktwfhyE0WTZgX/view?usp=sharing



FOOTNOTE

I also have an R9 Fury on the Celeron machine. When I run SRBMiner 0.1.5 in parallel with Claymore 15 mining ETH I got a small speed improvement of 0.8% on Claymore 15! Claymore reduced the performance of SRBMiner on RandomX by 15% when run in parallel.

[Marvell2]

whata the  performance on eaglesong on rx cards

[Marvell2]

also can you ad sigma for gulden cpu algo @Doctur

[tallman_ay]

R u going to update your miner with the new randomx for GPUs

[doktor83]

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

[doktor83]

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

[dragonmike]

This thread lacks highly important hashrate reports!...

Come on fellas, share your findings.

[doktor83]

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

[doktor83]

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.

[doktor83]

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 

RandomXL: ~ 63 h/s
RandomWow: ~ 88 h/s

[dragonmike]

RX Vega 56@64, core clk @ 1500mhz

CKB: ~ 673 MH/s