Pages:
Author

Topic: SRBMiner-MULTI GPU & CPU Miner 0.9.4 - page 45. (Read 42239 times)

hero member
Activity: 2422
Merit: 625
September 07, 2020, 02:49:59 AM
V0.5.0


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

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.
sr. member
Activity: 703
Merit: 272
September 07, 2020, 01:12:35 AM
V0.5.0


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

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?
hero member
Activity: 2422
Merit: 625
September 07, 2020, 12:04:36 AM
V0.5.0


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 Smiley
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 Smiley
sr. member
Activity: 703
Merit: 272
September 06, 2020, 08:01:49 PM
V0.5.0


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 Smiley
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.   
hero member
Activity: 2422
Merit: 625
September 06, 2020, 08:43:20 AM
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 Smiley
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.
newbie
Activity: 9
Merit: 0
August 31, 2020, 10:46:05 AM
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.
No worries.

That's what I assumed as well. The question is, since it was just a quick patch, how much work would it be for you to get it working on those older GCN cards again? Some of them would still be viable in XHV, especially with cheap power.
hero member
Activity: 2422
Merit: 625
August 22, 2020, 01:35:20 AM
doktor83,

sorry for bugging once again, but please respond to the issue about SRBMiner-CN 1.9.4 I reported here https://bitcointalksearch.org/topic/m.54900572

SRBMiner-CN 1.9.4 is still the fastest option on some CN altcoins that are somewhat viable on older hardware so it would be sad to lose this option.

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.
newbie
Activity: 194
Merit: 0
August 21, 2020, 05:30:19 AM
Looks like a great miner. We might be interested in integrating our coin with your miner.
newbie
Activity: 9
Merit: 0
August 20, 2020, 07:45:50 AM
doktor83,

sorry for bugging once again, but please respond to the issue about SRBMiner-CN 1.9.4 I reported here https://bitcointalksearch.org/topic/m.54900572

SRBMiner-CN 1.9.4 is still the fastest option on some CN altcoins that are somewhat viable on older hardware so it would be sad to lose this option.
hero member
Activity: 748
Merit: 523
August 07, 2020, 05:21:00 PM
Great. I will like a lot to test beta version if you need betatesters  Cheesy
hero member
Activity: 2422
Merit: 625
August 07, 2020, 02:50:25 PM
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  Cheesy.

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  Cool
hero member
Activity: 748
Merit: 523
August 07, 2020, 09:48:51 AM
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  Cheesy.
hero member
Activity: 2422
Merit: 625
August 07, 2020, 01:47:27 AM
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 ?

Our changes:
https://github.com/tevador/RandomX/compare/7567cef4c6192fb5356bbdd7db802be77be0439b...575d33f8620557e0b2cd0069d09a19a43f4aaede#diff-9e23bd2bad82d05cb017e4933a8c7b66

We have not implemented a stratum pool yet. Is it required? If so, we can make it happen.

If you want to attract more miners then yes, and my miner doesn't support solo mining, only stratum Smiley
hero member
Activity: 2422
Merit: 625
August 07, 2020, 01:46:23 AM
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:

Code:
* 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.

newbie
Activity: 194
Merit: 0
August 06, 2020, 01:53:15 PM
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 ?

Our changes:
https://github.com/tevador/RandomX/compare/7567cef4c6192fb5356bbdd7db802be77be0439b...575d33f8620557e0b2cd0069d09a19a43f4aaede#diff-9e23bd2bad82d05cb017e4933a8c7b66

We have not implemented a stratum pool yet. Is it required? If so, we can make it happen.
newbie
Activity: 315
Merit: 0
August 06, 2020, 09:22:16 AM
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:

Code:
* 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)
hero member
Activity: 2422
Merit: 625
August 06, 2020, 03:01:19 AM
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 ?
hero member
Activity: 2422
Merit: 625
August 06, 2020, 02:42:10 AM
If you think i'm wrong about miner, just for example XMRigCC:

Intel core i5:

Code:
* 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):

Code:
* 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.
newbie
Activity: 194
Merit: 0
August 06, 2020, 02:09:41 AM
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?
newbie
Activity: 315
Merit: 0
August 06, 2020, 01:52:55 AM
If you think i'm wrong about miner, just for example XMRigCC:

Intel core i5:

Code:
* 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) huge pages 0% 0/1168 +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):

Code:
* 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) huge pages 0% 0/1168 +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)
Pages:
Jump to: