Hi, first try removing the --cpu-threads 0 because that sets the number of threads to 1  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. |
|
|
|
|
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)
|
|
|
|
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 |
|
|
|
Doktor, can you compile win32 version of miner (at least for CPU algos)?
I can't sorry. The app i use to protect the binary is only x64 |
|
|
|
K12 is an old algo already available on FPGA no ?
It is. Just like a lot of algorithms  I've tested your new miner version on k12
it works well
this is just a testnet server right? I'm waiting the AEON fork, this is why I want be ready to mine on time
Yes, this is just a testnet so you can test your cpu/gpu/fpga before the fork |
|
|
|
V0.1.4 beta+ Fixed a critical bug with work creation for fast algorithms [k12, keccak] If you want to mine k12 or keccak algorithms with a rig, you should update to this version. Also here are some numbers for K12, but on cards that used to mine ETH: RX560 ~ 350 MHS [1180/1500] RX470 ~ 790 MHS [1130/1900] VEGA56 ~ 1770 MHS [1500/900] You should absolutely raise core clock and lower mem clock to get more hash. Test pool and address: {
"pool" : "162.210.173.150:4444",
"wallet" : "UmkHnTboxTobceosFgpM16CAkMZnwfqQCQrLY3zCZQLgEovYM72zpy21DjzS4vj8z3SrP3HWg6fKmSkcPz8oir5x1HDMQGKyn",
"password" : "x"
}
|
|
|
|
Ok, i found a bug in work creation, i just noticed this with the very fast K12 algo, where worker runs out of nonces very fast. Fix incoming soon |
|
|
|
V0.1.3 beta
+ Keccak algorithm +15% faster on gpu
+ K12 algorithm +8-12% faster on gpu [vega56 ~1700mhs]
+ Guided setup got smarter a little bit
have you made some tests for K12 algo on RX 4xx/5xx 4/8gb also? I'm asking cause I'm curious what clocks to use here tnx not really, but mem clock is not important, go as much high as you can with core clock There is one testpool i know about : 162.210.173.150:4444 |
|
|
|
|
V0.1.3 beta
+ Keccak algorithm +15% faster on gpu
+ K12 algorithm +8-12% faster on gpu [vega56 ~1700mhs]
+ Guided setup got smarter a little bit
|
|
|
|
In guided-setup I can set only standart address 10-12 characters, but pools use id address
Noo, you can set up to 200 characters for wallet address in guided setup mode, so that should fit the wallet.payment-id format too. I am happy that you have the best results with SRBMiner-MULTI |
|
|
|
Hello, DOK) Could you fix using ckb accound adress? Most pools in test phase using it.
I don't understand what should be fixed? Tested on sparkpool and hashpool, both work. Hi Dok - thanks for all your hard work on SRB.
Quick question, just trying to understand why you said Cryptonite algo coins are slowly dying and why CN miner support is EOL (end of life)?
Cryptunit.com has many CN projects and they are all very active in development - just trying to understand your reasoning behind this decision, maybe you will re-think it and continue support, it is a great miner. CN algo is also very active with many projects, duno maybe I'm missing something here. Anyways just trying to understand. Thanks in advance!
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. |
|
|
|
|
V0.1.2 beta
+ Added support for kangaroo12 algo [k12]
+ All algorithms that have a fee now have the same ~0.85% devfee
+ More bug fixes
Aeon will fork to k12 algo around Oct. 25th.
Unfortunately there are already FPGA bitstreams ready for this algo, but still, you should jump on GPU mining it at least a few days after the fork, cause it should be profitable.
Performance : ~1500MHS on Vega56 (40% faster than VulkanXMRMiner)
|
|
|
|
V0.1.1 beta
+Added yespowerltncg, yespowersugar, yespowerurx, yespower2b, eaglesong (nervos-ckb) algorithms
+Added support for SHA with yespower algorithm family
+Bug fixes
Hi Dok! Big fan of SRBminer AMD ; anyway you can implement argon2D-DYN aka argon2D-500? If not ofc i understand I will add a few from the argon family, but little later |
|
|
|
|
V0.1.1 beta
+Added yespowerltncg, yespowersugar, yespowerurx, yespower2b, eaglesong (nervos-ckb) algorithms
+Added support for SHA with yespower algorithm family
+Bug fixes
|
|
|
|
ok, i have an i5-2500k , it has same instruction set as your cpu, but 4 threads. With all 4 threads i get ~430hs, sse2 cause no sha available. No affinity set, just --cpu-threads 4 . I tried the miner from your link , 4 threads give approx the same result. I will compare these two on a few more machines, but i think there won't be such a drastical difference as in your case. How does your cmd line for SRB looks like ? Are you using the same affinity settings as with that other miner? |
|
|
|
As I was a regular user of SRB miner in the past I will follow this new topic to see the development for the new SRBMiner-MULTI
Good luck doktor83 with your new development
the cpu miner is very slow on cpupower  Intel 3770 cpupower opti 800 h/s on 4 threads srbminer 715 h/s on 8 threads or 430 h/s on 4 threads Which one is cpupower opti ? Also any other settings , like affinity used? |
|
|
|
|
Show Posts
