SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching

[henri2018]

V1.6.2
- Added support for Italocoin new algo (from block 55.000)
- Auto intensity for Vega cards improved, also managed to increase hashing speed on Vega cards for about ~1-1.5% (mainly on heavy algos)
- If user uses non existing GPU id in gpu_conf, it will be ignored, no error will be thrown
- Fixed miner crash when using a non AES capable CPU on some algos
- Added Windows version and build in log
- Added video driver version in log
- Added info about CPU AES support in log
- Statistics now shows number of stale shares that were accepted by pool
- Added parameter 'min_rig_speed_duration' that can set period for 'min_rig_speed' parameter (minimum is 30 sec), default is 5 min

+ I finally bought a Vega 56 card, so in the next releases i will try to improve the performance for Vegas. For now a little speedup of about 1-1.5% is achieved, mainly on Heavy based algos (Heavy, Haven, Bittube, Italo)

+ If you use a non existant id in gpu_conf, it will now be ignored, only id's that exist in your system will be used

+ There was a bug in soft AES that caused miner crash on Stellite and Haven algos, this is now fixed

+ Added accepted stale shares number in statistics. It can't know the number of real accepted stale shares on pool side, but the logic is simple, if a new job is received, but the miner sends a result in the mean time that is for the previous job, and this share gets accepted by the pool, miner will treat this like an accepted stale share.

+ min_rig_speed_duration can set the time you want to check the average hashrate for 'min_rig_speed' parameter. Default is 5 min.

Nice job, dok. For heavy algo, I don't need to run twice with intensity 60 first, and then 56. It is good now since intensity 56.

[1642506229]

1642506229

[1642506229]

1642506229

[1642506229]

1642506229

[1642506229]

1642506229

[1642506229]

1642506229

[UnclWish]

In 1.6.2 on cn-v7 algo intensity higher 100 not give jumps and drops in hashrate like it was on 1.6.1. But speed is low on v7... I tried 54,56,72,90,108,116 but all these intensities gives max 985 h/s on my RX 580 8Gb cards. On 1.6.0 I have 1030-1040 h/s...
Maybe I do something wrong? I tried to wait up to 10 min every try. But speed didn't jumps like in heavy algo. It pretty stable. Couse of it I didn't wait any longer.
Who got speed higher 1000 h/s on v7 with 1.6.2? Share your settings, please...

[NotEnough]

In 1.6.2 on cn-v7 algo intensity higher 100 not give jumps and drops in hashrate like it was on 1.6.1. But speed is low on v7... I tried 54,56,72,90,108,116 but all these intensities gives max 985 h/s on my RX 580 8Gb cards. On 1.6.0 I have 1030-1040 h/s...
Maybe I do something wrong? I tried to wait up to 10 min every try. But speed didn't jumps like in heavy algo. It pretty stable. Couse of it I didn't wait any longer.
Who got speed higher 1000 h/s on v7 with 1.6.2? Share your settings, please...

Same issue: 1.6.0 gets 1080 h/s on RX 588, but 1.6.2 - only 1025 h/s with same config.

[UnclWish]

In 1.6.2 on cn-v7 algo intensity higher 100 not give jumps and drops in hashrate like it was on 1.6.1. But speed is low on v7... I tried 54,56,72,90,108,116 but all these intensities gives max 985 h/s on my RX 580 8Gb cards. On 1.6.0 I have 1030-1040 h/s...
Maybe I do something wrong? I tried to wait up to 10 min every try. But speed didn't jumps like in heavy algo. It pretty stable. Couse of it I didn't wait any longer.
Who got speed higher 1000 h/s on v7 with 1.6.2? Share your settings, please...

Same issue: 1.6.0 gets 1080 h/s on RX 588, but 1.6.2 - only 1025 h/s with same config.

Samsung memory?

[NotEnough]

Samsung memory?

Yep, with Uber-Mix 3.1

[greerso]

V1.6.2
- Added support for Italocoin new algo (from block 55.000)
- Auto intensity for Vega cards improved, also managed to increase hashing speed on Vega cards for about ~1-1.5% (mainly on heavy algos)
- If user uses non existing GPU id in gpu_conf, it will be ignored, no error will be thrown
- Fixed miner crash when using a non AES capable CPU on some algos
- Added Windows version and build in log
- Added video driver version in log
- Added info about CPU AES support in log
- Statistics now shows number of stale shares that were accepted by pool
- Added parameter 'min_rig_speed_duration' that can set period for 'min_rig_speed' parameter (minimum is 30 sec), default is 5 min

+ I finally bought a Vega 56 card, so in the next releases i will try to improve the performance for Vegas. For now a little speedup of about 1-1.5% is achieved, mainly on Heavy based algos (Heavy, Haven, Bittube, Italo)

+ If you use a non existant id in gpu_conf, it will now be ignored, only id's that exist in your system will be used

+ There was a bug in soft AES that caused miner crash on Stellite and Haven algos, this is now fixed

+ Added accepted stale shares number in statistics. It can't know the number of real accepted stale shares on pool side, but the logic is simple, if a new job is received, but the miner sends a result in the mean time that is for the previous job, and this share gets accepted by the pool, miner will treat this like an accepted stale share.

+ min_rig_speed_duration can set the time you want to check the average hashrate for 'min_rig_speed' parameter. Default is 5 min.

Looks like you included Imperdin's heavy optimizations for that small bump.  Did you include that GPL3 code in your miner?

[doktor83]

V1.6.2
- Added support for Italocoin new algo (from block 55.000)
- Auto intensity for Vega cards improved, also managed to increase hashing speed on Vega cards for about ~1-1.5% (mainly on heavy algos)
- If user uses non existing GPU id in gpu_conf, it will be ignored, no error will be thrown
- Fixed miner crash when using a non AES capable CPU on some algos
- Added Windows version and build in log
- Added video driver version in log
- Added info about CPU AES support in log
- Statistics now shows number of stale shares that were accepted by pool
- Added parameter 'min_rig_speed_duration' that can set period for 'min_rig_speed' parameter (minimum is 30 sec), default is 5 min

+ I finally bought a Vega 56 card, so in the next releases i will try to improve the performance for Vegas. For now a little speedup of about 1-1.5% is achieved, mainly on Heavy based algos (Heavy, Haven, Bittube, Italo)

+ If you use a non existant id in gpu_conf, it will now be ignored, only id's that exist in your system will be used

+ There was a bug in soft AES that caused miner crash on Stellite and Haven algos, this is now fixed

+ Added accepted stale shares number in statistics. It can't know the number of real accepted stale shares on pool side, but the logic is simple, if a new job is received, but the miner sends a result in the mean time that is for the previous job, and this share gets accepted by the pool, miner will treat this like an accepted stale share.

+ min_rig_speed_duration can set the time you want to check the average hashrate for 'min_rig_speed' parameter. Default is 5 min.

Looks like you included Imperdin's heavy optimizations for that small bump.  Did you include that GPL3 code in your miner?

It just looks like, but dont worry imperdin, as i already told you i dont need to use your crazy insane mega giga optimisations. I already got even more speed increase since we talked, so if you plan releasing another mega giga optimisation please dont do it before i release the next version of miner.

[doktor83]

In 1.6.2 on cn-v7 algo intensity higher 100 not give jumps and drops in hashrate like it was on 1.6.1. But speed is low on v7... I tried 54,56,72,90,108,116 but all these intensities gives max 985 h/s on my RX 580 8Gb cards. On 1.6.0 I have 1030-1040 h/s...
Maybe I do something wrong? I tried to wait up to 10 min every try. But speed didn't jumps like in heavy algo. It pretty stable. Couse of it I didn't wait any longer.
Who got speed higher 1000 h/s on v7 with 1.6.2? Share your settings, please...

Same issue: 1.6.0 gets 1080 h/s on RX 588, but 1.6.2 - only 1025 h/s with same config.

guys what is your 30 min average speed in statistics 1.6.0 vs 1.6.2?

[ipe4enko]

In 1.6.2 on cn-v7 algo intensity higher 100 not give jumps and drops in hashrate like it was on 1.6.1. But speed is low on v7... I tried 54,56,72,90,108,116 but all these intensities gives max 985 h/s on my RX 580 8Gb cards. On 1.6.0 I have 1030-1040 h/s...
Maybe I do something wrong? I tried to wait up to 10 min every try. But speed didn't jumps like in heavy algo. It pretty stable. Couse of it I didn't wait any longer.
Who got speed higher 1000 h/s on v7 with 1.6.2? Share your settings, please...

Same issue: 1.6.0 gets 1080 h/s on RX 588, but 1.6.2 - only 1025 h/s with same config.

guys what is your 30 min average speed in statistics 1.6.0 vs 1.6.2?

It's not my questions. But on srb 1.6.1- 1.6.2 i see lower performance about 50 h/s on one rx550 card. If need i can publish logs.
On the same configs. Perhaps we need to change configuration, intensity or worksize?

[NotEnough]

guys what is your 30 min average speed in statistics 1.6.0 vs 1.6.2?

1080 vs 1024

[WebTosha]

Good afternoon, doctor. I have a 13-card rig.
1) 9 cards of Sapphire RX550 / 2Gb on baffin
2) 1 card of Sapphire RX550 / 2 Gb on gfx804
3) 3 cards of MSI AERO RX550 / 2 GB on gfx804

On version 1.6.0, all cards worked with parameters 26.3 / 12 and issued:
1) at 497 h/s
2) 498 h/s
3) at 513 h/s

to my great regret at the transition to 1.6.1, and now on 1.6.2 with the same parameters of the cards began to give different results. In particular
The cards from point (1) remained at the same values, and from point (2) and (3) began to jump from 410 to 480 h/s. By reducing the parameters to 22.1/12 I was able to achieve a stable speed on the MSI cards from (3)  of 499 h/s, but could not achieve an acceptable speed on the card from point (2). I went through all the intensity options from 18 to 28 in steps of 0.1 the maximum stable result was reached at 22.1 / 12 at 475 h/s.

[Mike Leone]

Hello, does not display the temperature and speed of the fan. Video cards R9 370 series ...

Try to change adl_type parameter, default is 1, try 2.
Put it on "gpu_conf" to get something like that (for intensity, worksize e threads use your stable config, this is only for example):

"gpu_conf" :
[
   { "id" : 0, "intensity" : 50, "worksize" : 4, "threads" : 1, "adl_type": 2},
]


"adl_type" : 1 or 2 , 1 - USE OVERDRIVEN , 2 - USE OVERDRIVE 5. Default is 1 if not set. Option 2 (Overdrive 5) is suitable for older cards

Thank you so much bro!!!

[doktor83]

guys what is your 30 min average speed in statistics 1.6.0 vs 1.6.2?

1080 vs 1024

Strange, really. I have 580 8g (hynix) cards i tested the miner on , and i get the same hashrate on V7 as on previous versions.
There are always HR fluctuations, and always will be, that's why i ask for the 30 min average, and not the value you get when pressing 'h'.

Same rig, same driver, same everything except miner version?

I will check to see if any of the changes i made could cause this HR drop.

[SmartOdissey]

with 1.6.0 - 8400
with 1.6.2 - 8800

Tell me pls Docta, why RX580-8gb have 1100h/s with old blockchain drivers, and 800h/s with  18.5.x in same system?

[sweetydady]

why the miner just won't start with ryo coin?? it exits just on start

[NotEnough]

Same rig, same driver, same everything except miner version?

Yes.

why the miner just won't start with ryo coin?? it exits just on start

Add command "pause" in the end of .bat file and you will see some messages.

[lebuawu2]

with 1.6.0 - 8400
with 1.6.2 - 8800

Tell me pls Docta, why RX580-8gb have 1100h/s with old blockchain drivers, and 800h/s with  18.5.x in same system?

did you already set compute mode?

[sweetydady]

Same rig, same driver, same everything except miner version?

Yes.

why the miner just won't start with ryo coin?? it exits just on start

Add command "pause" in the end of .bat file and you will see some messages.

nothing. black comand line window appears on start and exits immediately

[dragonmike]

Livada,

can you show 24 hours average, or hash count since start of the miner?

dingdongtobias,
thanks for the link, I will update them over there. I did not pay attention to CAST so much, as I never liked that miner and moved immediately away, so i have 0 screenshots, proofs or research.

i can't find any of your screenshots for srb neither, probably because there aren't any.

Here is my screenshot 24h average on nanopool :
https://bitcointalk.org/index.php?topic=3167363.msg40640415#msg40640415

Also I did a 6 hour test for Xmr Stak you said it shows you the exact same hashrate like the pool side, but not in my case :
https://bitcointalk.org/index.php?topic=3167363.msg41077478#msg41077478

JCE I did not test yet, but i will give it a try.

Also DragonMike, where are your screenshots? Are you even using srbminer ?

I actually don't need to post any screenshots because I made the mistake of believing the ramblings of a forum noob.

Just ran SRBMiner 1.6.0 on one of my 7x RX 570 rigs for 24 hours on Nanopool. Mining XMR (normalv7).

Average hashrate on the pool was less than 1% lower than reported hashrate from the miner.

@Doktor83: apologies for asking you to answer for non-existing issues. Constantly having to look for more profitability in these difficult times makes me tired, obviously!

[lebuawu2]

nothing. black comand line window appears on start and exits immediately

can you post your .bat file?