|
Yes, when there will be a pool for it
|
|
|
|
Oh sh*t, thanks SChernykh, i will report it too right now |
|
|
|
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  |
|
|
|
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. |
|
|
|
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 ? |
|
|
|
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  |
|
|
|
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 : ~340MHSVega56 [56 cu] 1450/940 : ~1700MHS |
|
|
|
|
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
|
|
|
|
Which algorithm are you mining ?
What are your GPU settings ?
I am sure someone with Vii cards can help you.
Lot of people use SRBMiner + VII without problems.
algorithm CN haven voltage 981 mV core clock 1649 Mhz mem clock 1100 Mhz its about 2600 h/s each card cryptonight haven power consumption 130 watt in adrenalin drivers log Try this : If you use configuration file, add "heavy_mode" : 2, or if you use cli parameters add --cgpuheavymode 2. This will give you a little lower hashrate but will get rid of compute errors. Come to SRBMiner discord, i can help you faster there : https://discord.gg/zXY23De |
|
|
|
Probably freez problem was really in accidentally click in the window.
I didn 't expect click in the window miner its a pause command.
after untick Edit Options : Quick Edit Mode already 20 hours miner is working without freez. test is keep going
thanks!
It is a windows 10 thing, if quick edit mode is enabled you pause any console application execution with only clicking in the window... tried various options intensity, voltage, clocks settings, change pci-e and rizers, but any of GPU crashed some time and I get this log:
Compute Errors
-------------
[90] : BUS_ID7
[5] : BUS_ID23
[6] : BUS_ID3
[188] : BUS_ID10
[5] : BUS_ID19
Which algorithm are you mining ? What are your GPU settings ? I am sure someone with Vii cards can help you. Lot of people use SRBMiner + VII without problems. |
|
|
|
Hello every one
need help
what to do if SRB is freez after 15-20 min ? Its mean pool statistics go to zero and miner window is freez until any key is pressed.
it means no user actions every 15 minutes - no mining
GPU AMD radeon VII (set 1600 mhz, 891 mV)
win 10 x64
virt mem - 64 gb
If I press any key SRB miner reastart log:
[2019-11-16 14:29:39] ADL2_OverdriveN_Temperature_Get for ADL index 23 failed.
[2019-11-16 14:29:39] ADL2_OverdriveN_Temperature_Get for ADL index 31 failed.
[2019-11-16 14:29:39] ADL2_OverdriveN_Temperature_Get for ADL index 31 failed.
[2019-11-16 14:29:39] ADL2_OverdriveN_Temperature_Get for ADL index 39 failed.
[2019-11-16 14:29:39] ADL2_OverdriveN_Temperature_Get for ADL index 39 failed.
[2019-11-16 14:24:51] json_send[201]: {"id":79,"jsonrpc": "2.0","method":"submit","params":{"id":"710651929082285","job_id":"958516488688901","nonce":"d5320100","result":"c810904070223c6cfeba102bebd5106441091c6edb4e372ae1ab392f0c090000"}}
[2019-11-16 14:29:39] ADL2_OverdriveN_FanControl_Get for ADL index 15 failed.
[2019-11-16 14:29:39] miner_result: GPU128[BUS:-1] result rejected [invalid job id]
[2019-11-16 14:29:39] json_receive[72]: {"id":79,"jsonrpc":"2.0","error":{"code":-1,"message":"Invalid job id"}}
[2019-11-16 14:29:39] watchdog: GPU0 [BUS:3] DEAD
[2019-11-16 14:29:40] watchdog: GPU crash detected, miner will try to restart
[2019-11-16 14:29:40] miner_result: GPU4[BUS:23] result rejected [invalid job id]
[2019-11-16 14:29:40] json_receive[275]: {"jsonrpc":"2.0","method":"job","params":{"blob":"0505e3b9bfee055ec173997252c20e1fddc60cff8d84da48138685dde7c2367dd3dd62621640d60 00000002e4aaca5ca965e161bd42f9129e8aef9555a233c79ab9c8fa0b4200cedb93a8d01","job_id":"760811658670313","target":"caac0000","id":"710651929082285"}}
[2019-11-16 14:29:40] json_receive[72]: {"id":79,"jsonrpc":"2.0","error":{"code":-1,"message":"Invalid job id"}}
[2019-11-16 14:29:40] miner_result: GPU0[BUS:3] result rejected [invalid job id]
[2019-11-16 14:29:40] json_receive[275]: {"jsonrpc":"2.0","method":"job","params":{"blob":"0505e3b9bfee055ec173997252c20e1fddc60cff8d84da48138685dde7c2367dd3dd62621640d60 0000000469b38f556a973a2d28eef4f82c70cae29138f0493b7b71b93180b79ee5c18c501","job_id":"181959531151042","target":"94590100","id":"710651929082285"}}
[2019-11-16 14:29:40] pool_have_job: Job received [ID: 898705469323995]
[2019-11-16 14:29:40] hashrate: GPU0: 2555 H/s [T:0c][BUS:3]
[2019-11-16 14:29:40] ADL2_OverdriveN_Temperature_Get for ADL index 7 failed.
[2019-11-16 14:29:40] Restarting miner...
Thank you !
One of your GPU's crashes? [2019-11-16 16:30:04] GPU crash detected, miner will try to restart This could be cause from too low voltage, and too high clocks for example. Too high intensity setting... The other thing: If you click in the console window that pauses process until you press any key in the miner window. (quick edit mode enabled). Try : right click on console window title -> properties -> untick Edit Options : Quick Edit Mode. This way you can't accidentally click in the window and pause the process. Come to discord : https://discord.gg/zXY23De |
|
|
|
Hello @doktor83 ! This is my test... What a poor result as an i7-8750H :/ [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. |
|
|
|
Still need to improve the auto selection of best config for randomx  |
|
|
|
This thread lacks highly important hashrate reports!...
Come on fellas, share your findings.
i5-2500K CPU @ 3.30GHz @ 3 threadsRandomX: ~ 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 |
|
|
|
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 |
|
|
|
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 0x0000FFFFFFFFFFFFfor 48 threads --cpu-threads 46 --cpu-affinity 0x00003FFFFFFFFFFF |
|
|
|
|
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
|
|
|
|
|
Show Posts
