Thank you for dual mining!
Can you please add ProgPowEpic for dual mining?
Sorry but no, not worth my time. |
|
|
|
V0.5.0You definitely need to check out HELP and EXAMPLES folders because a lot of things changed from previous version!Total reorganisation, new features etc.. Hope a lot of you find it useful  I will make a few video tutorials when i get some free time on how to use the new multi algorithm feature. Until then look in 'Examples' and 'Help' folder to get some clue on how to use the new feature. does the "," (i.e. comma) delineation between gpu not work anymore, or is it now only "!" now. Yes, it's ! now, check the examples folder it contains a bunch of good examples Is there a chance to add the "," back? it's just the "!" is non-standard and not used in any other miners... that i know of. the "!" makes it more difficult for multi-miners that used multiple programs. Also, do you now support NAVI on all gpu algo? I had to use a 'non standard' character because of the password field for example, which is used on a lot of pools to pass additional data, and they are comma separated. That's why i chose ; and ! because those are not used (probably) in wallet address, pool url, password field etc.. Also wanted it to be same for every parameter and not leave comma for gpu-id for example but use ! on others.. Hopefully software that uses SRB will adapt to the new format. |
|
|
|
V0.5.0You definitely need to check out HELP and EXAMPLES folders because a lot of things changed from previous version!Total reorganisation, new features etc.. Hope a lot of you find it useful I will make a few video tutorials when i get some free time on how to use the new multi algorithm feature. Until then look in 'Examples' and 'Help' folder to get some clue on how to use the new feature. does the "," (i.e. comma) delineation between gpu not work anymore, or is it now only "!" now. Yes, it's ! now, check the examples folder it contains a bunch of good examples |
|
|
|
V0.5.0+ Now supporting real MULTI ALGORITHM mining, you can mine up to 4 algorithms at the same time + Changed API and WEB stats to be compatible with the new multi algorithm mining functionality + Added GPU auto tune functionality + A lot of changes in configuration parameters and the way you define them (check Help folder) + Updated algorithm 'defyx' to 'panthera' + Updated algorithm 'tellor' to work on tellorpool.org, and removed devfee + Added algorithm 'cryptonight_ccx' + Added algorithm 'cryptonight_xhv' + Added algorithm 'cryptonight_gpu' + Added algorithm 'cryptonight_upx' + Added algorithm 'cryptonight_heavyx' + Added algorithm 'verushash' + Added new parameters '--gpu-auto-tune', '--multi-algorithm-job-mode', '--cpu-threads-intensity', '--gpu-auto-intensity', '--gpu-cn-mode' + Parameter '--gpu-ethash-mode' now has a new mode : 3 + A lot of bug fixes You definitely need to check out HELP and EXAMPLES folders because a lot of things changed from previous version!Total reorganisation, new features etc.. Hope a lot of you find it useful I will make a few video tutorials when i get some free time on how to use the new multi algorithm feature. Until then look in 'Examples' and 'Help' folder to get some clue on how to use the new feature. Also for you guys that mine Ethash with 4GB gpu's, i added --gpu-ethash-mode 3 (it should be auto used if possible), which needs you to have 1 8GB AMD gpu and at least 5GB of system RAM.
|
|
|
|
Hi, sorry i missed your message. 1.9.4 is just a quick patch for Haven, and yes i probably screw up some things.. Im not maintaining the CN version anymore, just wanted to give an option for XHV miners who want to continue using SRBMiner. For all the rest algorithms just use 1.9.3 version. |
|
|
|
Hi doktor83, Scala (XLA) changes mining algorithm a week ago. No more Defyx, now is Panthera algo. May you want to update your miner?. SRBminer was really faster than official miner on Defyx  . Next release will contain the change (but its ~ same speed as xlarig unfortunately) and also a ton of new stuff. Just need a few more weeks  |
|
|
|
If you want to attract more miners then yes, and my miner doesn't support solo mining, only stratum |
|
|
|
I will not argue with you about allocated or not in huge(large) pages, but XMRigCC hashing 2x times faster then SRBminer on this processors, so looks like it use huge pages. This is how log looks on Intel Celeron without enough L3 cache size: * ABOUT XMRigCC/2.7.0 gcc/10.1.0 (RELEASE)
* LIBS libuv/1.38.0 OpenSSL/1.1.1g hwloc/2.2.0
* HUGE PAGES permission granted
* CPU Intel(R) Celeron(R) CPU J1900 @ 1.99GHz (1) x64 -AES
L2:2.0 MB L3:0.0 MB 4C/4T NUMA:1
* DONATE 1%
* ASSEMBLY auto:none
* POOL #1 ********* algo rx/0
* COMMANDS hashrate, pause, resume, quit
[2020-08-06 17:10:29.950] CC feature is disabled.
[2020-08-06 17:10:30.777] net use daemon ************ TLSv1.2 *************
[2020-08-06 17:10:30.780] net fingerprint (SHA-256): "***************************"
[2020-08-06 17:10:30.781] net new job from ******** target 000009375d366e6c algo rx/0 height 119187
[2020-08-06 17:10:30.784] rx init dataset algo rx/0 (4 threads) seed 4181a493b397a733...
[2020-08-06 17:10:30.791] rx allocated 2336 MB (2080+256) huge pages 0% 0/1168 +JIT (4 ms)
[2020-08-06 17:10:54.601] rx dataset ready (23806 ms)
[2020-08-06 17:10:54.604] cpu use profile rx/0 (2 threads) scratchpad 2048 KB
[2020-08-06 17:10:54.647] cpu READY threads 2/2 (2) huge pages 0% 0/2 memory 4096 KB (40 ms) Maybe hashes 2x faster but still the dataset is not allocated in huge pages. ( huge pages 0% 0/1168 ) Look how that line should look when dataset is allocated successfully in HP mem.  |
|
|
|
YadaCoin may be interested in integrating our algo into your miner. We're a RandomX variant. Is it possible for our coin to be integrated into your main release?
Hi, can you give me a link to your github so i can see the changes you made with RX ? Also is there a stratum pool for your coin ? |
|
|
|
If you think i'm wrong about miner, just for example XMRigCC: Intel core i5: * ABOUT XMRigCC/2.7.0 gcc/10.1.0 (RELEASE)
* LIBS libuv/1.38.0 OpenSSL/1.1.1g hwloc/2.2.0
* HUGE PAGES permission granted
* CPU Intel(R) Core(TM) i5-4670 CPU @ 3.40GHz (1) x64 AES
L2:1.0 MB L3:6.0 MB 4C/4T NUMA:1
* DONATE 1%
* ASSEMBLY auto:intel
* POOL #1 ********** algo rx/0
* COMMANDS hashrate, pause, resume, quit
[2020-08-06 08:44:58.286] CC feature is disabled.
[2020-08-06 08:44:59.202] net use daemon ********* TLSv1.2 ***********
[2020-08-06 08:44:59.206] net fingerprint (SHA-256): "f4fa3fae42315e4ad55027451ececc9768d2b7403e5a8ef859dd1ab83df9a152"
[2020-08-06 08:44:59.208] net new job from ******** target 0000054899c39bd5 algo rx/0 height 119123
[2020-08-06 08:44:59.211] msr service WinRing0_1_2_0 is already exists
[2020-08-06 08:44:59.215] rx init dataset algo rx/0 (4 threads) seed 4181a493b397a733...
[2020-08-06 08:44:59.685] rx allocated 2336 MB (2080+256) [b]huge pages 0% 0/1168[/b] +JIT (468 ms)
[2020-08-06 08:45:07.523] rx dataset ready (7836 ms)
[2020-08-06 08:45:07.524] cpu use profile * (1 thread) scratchpad 2048 KB
[2020-08-06 08:45:07.526] cpu READY threads 1/1 (1) huge pages 100% 1/1 memory 2048 KB (1 ms) and even old Intel Xeon E5520 (which even not support intel optimization): * ABOUT XMRigCC/2.7.0 gcc/10.1.0 (RELEASE)
* LIBS libuv/1.38.0 OpenSSL/1.1.1g hwloc/2.2.0
* HUGE PAGES permission granted
* CPU Intel(R) Xeon(R) CPU E5520 @ 2.27GHz (1) x64 -AES
L2:1.0 MB L3:8.0 MB 4C/8T NUMA:1
* DONATE 1%
* ASSEMBLY auto:none
* POOL #1 ********* algo rx/0
* COMMANDS hashrate, pause, resume, quit
[2020-08-06 08:40:56.331] CC feature is disabled.
[2020-08-06 08:40:57.269] net use daemon ******** TLSv1.2 ***********
[2020-08-06 08:40:57.271] net fingerprint (SHA-256): "f4fa3fae42315e4ad55027451ececc9768d2b7403e5a8ef859dd1ab83df9a152"
[2020-08-06 08:40:57.272] net new job from ********** target 0000054899c39bd5 algo rx/0 height 119123
[2020-08-06 08:40:57.282] rx init dataset algo rx/0 (8 threads) seed 4181a493b397a733...
[2020-08-06 08:40:57.375] rx allocated 2336 MB (2080+256) [b]huge pages 0% 0/1168[/b] +JIT (90 ms)
[2020-08-06 08:41:10.746] rx dataset ready (13367 ms)
[2020-08-06 08:41:10.748] cpu use profile rx/0 (2 threads) scratchpad 2048 KB
[2020-08-06 08:41:10.800] cpu READY threads 2/2 (2) huge pages 100% 2/2 memory 4096 KB (50 ms) Sorry but you are wrong, you can see in the log you pasted that xmrig also isn't allocating the dataset in huge pages ( huge pages 0% 0/1168 ). It should be huge pages 100% 1168/1168. Like you see lower there : READY threads 2/2 (2) huge pages 100% 2/2 that the scratchpad for the threads was allocated in HP. |
|
|
|
Hi, Doktor83! Will you plan to fix RandomX Huge/Large pages allocation for Intel I5 processors windows 7?
Coz it not work.
There is nothing to fix specifically for that processor or win7, miner uses windows mechanisms to allocate mem in huge pages, so it should work same with every cpu First make sure you have enough RAM (4gb for example), and that you tried to run miner after computer restart, so that there are still free pages available for miner to allocate. |
|
|
|
Hello, I want to start mining. What is the best miner for use with AMD FX 6100 CPU and 2 AMD GPUs (older ones)  And where can I get it on githhub??? I read a little bit here in this thread and don`t want to download the wrong miner... XMR stak??? Thanks for your help Old CPU and GPUs, you can try JCE CN miner. It's not developed anymore, but it supports old AMD hardware. And won't work because there was a fork few days ago.. Try Xmrig |
|
|
|
Is it possible to mine tellor now? Coz uupool no more support tellor coin.
Then not possible. I tried to contact hashpool but never got a response. That's the reason why only uupool was supported. I will try to contact him again. |
|
|
|
Thank you for answers. How about to add cuckaroo/cuckatoo algos for cpu (grin/epic have some ocl and cpu plugins) and gpu?
Hi, not atm, but maybe once in the future. There are a lot of other algorithms i would like to add too |
|
|
|
V0.4.7+ Removed devfee for 'blake2s', 'mtp', 'keccak', 'yespoweritc', 'm7mv2', 'cryptonight_catalans', 'cryptonight_talleo' algorithms + Lowered 'bl2bsha3' devfee to standard fee (~0.85%) + Fixed 'randomx' algorithm when running on 64+ threads + Fixed config parameter "cpu_affinity" - Now you get even more 0% devfee algorithms - Thanks to @Zorg33 ( https://github.com/doktor83/SRBMiner-Multi/issues/10) managed to fix 'randomx' too low hashrate when running with 64+ threads - "cpu_affinity" parameter in configuration file was not working, now it is fixed
|
|
|
|
Hi, Doktor. Any plans to add dual mining for RandomEpic/ProgPow for epic coin?
Another question - if i have one card with 8gb and other with 4gb can miner use first card 8gb memory
for DAG so second card with 4gb memory can continue mine eth after dag size >=4 gb?
Hi, no dual mining is in plan at the moment. And no, what you would like with the 8g-4g is not possible |
|
|
|
|
V0.4.6
+ Fixed 'defyx' algorithm on Intel CPU's (previous version broke it)
+ Hashrate stats (pressing 'h') now shows current hashing speed of CPU, and not the 10 second average
+ Lowered pool reconnection time to 15 sec
+ Added parameter '--gpu-ethash-mode' to cmd parameters
+ Added parameter 'gpu_ethash_mode' to config parameters
+ Added parameter 'ethash_mode' to gpu_conf parameters
+ Added parameter '--disable-cpu-auto-affinity'
- parameter ethash mode, if set to 1, will allow for a little more memory allocation of DAG on the GPU, so if you are really on the edge of the limit, this could help you mine with normal speed for few more epochs. The bad thing is, if your gpu is on pcie 1.0 (riser) then the DAG creation time will be very high, rx580 is about 50 minutes. Also you should only use it with Ethereum, because the devfee is mining ETH, so imagine if you mine ETC , it takes 50 minutes to created DAG, and then on devfee mining again 50 minutes to create DAG for ETH..
- parameter --disable-cpu-auto-affinity turns off the automatic affinity setting, and leaves that to the OS to manage.
|
|
|
|
Hi Doktor, can we dual mine Epic and other RandomX coin while Epic RandomX is idle?
No, it's not working that way, sorry. |
|
|
|
V0.4.5+ Added 'randomepic' algorithm (EpicCash RandomX) solo/pool + 'ethash' and 'ubqhash' algorithm faster ~1.5% on Vega + 'RandomX' algorithm improvements + Fixed allocation of 'RandomX' dataset for 1Gb pages (--randomx-use-1gb-pages parameter) + Fixed an issue with MSR tweaks not being applied correctly + Lowered 'minotaur' algorithm devfee to 2% + Fixed crashing of 'minotaur' algorithm on AVX2 capable cpu's + '--send-stales' is now set per pool, it accepts true/false. Default is true. + 'send_stales' parameter added to pools config file too + '--gpu-intensity' option can now be used in combination with auto gpu setup in cmd + Improved gpu watchdog + Added temporary parameter '--cnpool-bbc-fix' which disables workers if job diff >= 50 + Minor bug fixes - When mining 'randomepic' miner workers will stop when jobs are not randomx. - Found a bug that was here from the beginning of randomx addition, where MSR tweaks were applied incorrectly, so the hashrate was lower than it could be. - '--send-stales' and send_stales parameters now accept a bool (true, false) and are now set per pool. Some pools accept stales while others don't, with this parameter you can control to which pool you want to send/not send shares that miner thinks are stale. Default is true, it means stale shares are sent if this parameter is not set to false. - added parameter '--cnpool-bbc-fix' on request of cnpool.cc operator. If this parameter is used miner will stop workers when a job diff >= 50 received. - Now you can use '--gpu-intensity' parameter alone, and miner will set the rest parameters for you automatically. Example : 1. Set same intensity to every gpu:SRBMiner-MULTI.exe --algorithm ethash --gpu-intensity 24 --disable-cpu --pool eth-eu1.nanopool.org:9999 --wallet 0x74fb183Dfa951A9dC8C6de5ae4E1A8587fa6f371
SRBMiner-MULTI.exe --algorithm ethash --gpu-intensity 24,23,23,25 --disable-cpu --pool eth-eu1.nanopool.org:9999 --wallet 0x74fb183Dfa951A9dC8C6de5ae4E1A8587fa6f371
Also from previous version the '--gpu-tweak-profile' parameter works the same, so it can be applied without setting the rest of the gpu parameters. Example: 1. Apply intensity 24 to every gpu and set tweak-profile 5 to themSRBMiner-MULTI.exe --algorithm ethash --gpu-intensity 24 --gpu-tweak-profile 5 --disable-cpu --pool eth-eu1.nanopool.org:9999 --wallet 0x74fb183Dfa951A9dC8C6de5ae4E1A8587fa6f371
|
|
|
|
|
Show Posts
