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

[mk111]

Here's a nice little tip on how to increase your hashrate even more :
Example for Vega56 doing normalv7 algo :

1.Put --enableduplicategpuid in start.bat at the end of line ( SRBMiner-CN.exe --config config-normalv7.txt --pools pools-normalv7.txt  --sendallstales --enableduplicategpuid )
2.Set gpu in config-normalv7.txt :

Code:

{
"cryptonight_type" : "normalv7",
"intensity" : 0,
"double_threads" : true,
"gpu_conf" : 
[ 
	{ 
	  "id" : 0, 
	  "intensity" : 122, 
	  "worksize" : 8, 
	  "threads" : 1
	},
	{ 
	  "id" : 0, 
	  "intensity" : 124, 
	  "worksize" : 8, 
	  "threads" : 1
	}
]
}

What was done here?  When using 2 threads , the best value for intensity is 123. By enabling the usage of duplicate gpu id, you make 2 separate threads for 1 gpu, but one has value 123-1, the other 123+1.
This method can be used on any GPU, you just need to experiment with the intensities.

Awesome I will try it later.
How much increase did you get with 1 x Vega 56?
Mine does 2028H/s per card at the moment.

[wgestickley]

Hey,

while playing around with auto switch, I was wondering, if there is an detailed overview for GPUs with best settings and intensity’s For SRB Miner?!

[doktor83]

Hey,

while playing around with auto switch, I was wondering, if there is an detailed overview for GPUs with best settings and intensity’s For SRB Miner?!

you can find a few in the first post, those are some numbers users posted here.

[wgestickley]

Hey,

while playing around with auto switch, I was wondering, if there is an detailed overview for GPUs with best settings and intensity’s For SRB Miner?!

you can find a few in the first post, those are some numbers users posted here.

Yes, I saw them. But actually not for my cards. I would love to get those number for RX570 and RX580. Is anybody so kind to share?

@Doc: why not collect all of this data on you Homepage? Perhaps for new User it is very interesting to check quick which Algo amd which card needs which threads and intensity?

[livada]

Here's a nice little tip on how to increase your hashrate even more :
Example for Vega56 doing normalv7 algo :

1.Put --enableduplicategpuid in start.bat at the end of line ( SRBMiner-CN.exe --config config-normalv7.txt --pools pools-normalv7.txt  --sendallstales --enableduplicategpuid )
2.Set gpu in config-normalv7.txt :

Code:

{
"cryptonight_type" : "normalv7",
"intensity" : 0,
"double_threads" : true,
"gpu_conf" : 
[ 
	{ 
	  "id" : 0, 
	  "intensity" : 122, 
	  "worksize" : 8, 
	  "threads" : 1
	},
	{ 
	  "id" : 0, 
	  "intensity" : 124, 
	  "worksize" : 8, 
	  "threads" : 1
	}
]
}

What was done here?  When using 2 threads , the best value for intensity is 123. By enabling the usage of duplicate gpu id, you make 2 separate threads for 1 gpu, but one has value 123-1, the other 123+1.
This method can be used on any GPU, you just need to experiment with the intensities.

Awesome I will try it later.
How much increase did you get with 1 x Vega 56?
Mine does 2028H/s per card at the moment.

in tube-haven-havy you lose 20HR per card with this i not try in v7 and fast
56 is best
55/57 - 56/57 -55/56 - 56/58 - all is worse.

[ikyo]

Here's a nice little tip on how to increase your hashrate even more :
Example for Vega56 doing normalv7 algo :

1.Put --enableduplicategpuid in start.bat at the end of line ( SRBMiner-CN.exe --config config-normalv7.txt --pools pools-normalv7.txt  --sendallstales --enableduplicategpuid )
2.Set gpu in config-normalv7.txt :

Code:

{
"cryptonight_type" : "normalv7",
"intensity" : 0,
"double_threads" : true,
"gpu_conf" : 
[ 
	{ 
	  "id" : 0, 
	  "intensity" : 122, 
	  "worksize" : 8, 
	  "threads" : 1
	},
	{ 
	  "id" : 0, 
	  "intensity" : 124, 
	  "worksize" : 8, 
	  "threads" : 1
	}
]
}

What was done here?  When using 2 threads , the best value for intensity is 123. By enabling the usage of duplicate gpu id, you make 2 separate threads for 1 gpu, but one has value 123-1, the other 123+1.
This method can be used on any GPU, you just need to experiment with the intensities.

I tried this on my Vega 64's and saw a nice little bump for not doing much.  I was able to squeeze out between 15 and 20h/s per card.  So that really adds up pretty quickly.  Now I am going to cry and say it messes up my monitoring   I now see duplicate GPU's.

[dopper]

Mine does 2028H/s per card at the moment.

care to share your config/clocks/voltage? please

[mk111]

Mining Stellite with 4 Vega 56.

https://imgur.com/a/aKgf6rt

[mk111]

Extra 21H/s per Vega 56 when using Doc's new trick
Now my Vega 56's do 2049H/s per card.

Anyone getting better results with reference Vega 56's?

[Vince34]

Me 

[mk111]

Me 

LOL so tell us how...

[Vince34]

Me 

LOL so tell us how...

Haha,
I have 4 VEGA 56 (3 ref & 1 peace of sh..)
I was at 7500-7520h/s  and now  I'm at 7620-7630h/s with the same "summer" profile (CC:1340Mhz / MC:900Mhz)
But I'm not sure all the speed up come from the duplicategpuid trick because I updated drivers (from blockchain to 18.6.1) and SRBMiner (from 1.5.5.1 to 1.6.6) at the same time.

[jimmyD30]

Anyone experience increased HR with v1.6.6 over v1.6.5 using Vega64s (without the trick)?

[dragonmike]

I've got a question about the reboot script when using pool switching: do you have to set it for each algo separately or can you just add it at the end of the start.bat command line?

[livada]

Me  

LOL so tell us how...

Haha,
I have 4 VEGA 56 (3 ref & 1 peace of sh..)
I was at 7500-7520h/s  and now  I'm at 7620-7630h/s with the same "summer" profile (CC:1340Mhz / MC:900Mhz)
But I'm not sure all the speed up come from the duplicategpuid trick because I updated drivers (from blockchain to 18.6.1) and SRBMiner (from 1.5.5.1 to 1.6.6) at the same time.

just remove duplicatedgpuid and see. i thinhk driver  up HR. duplicated gpuid not work for me.
HR is identical or  smaller with this otpion for me.
3*referal vega56 with 64 bios(1-2-4card) + 1 vega64LE(stock bios)(3card)=700W from the wall(tube) and 720W(xtl)
ver 1.6.4 + driver 1.8.34 standard option without --enableduplicategpuid
algo: tube and stellite

https://image.prntscr.com/image/_QihwWeLTQiGRpgtx9N3nQ.jpg

https://image.prntscr.com/image/lZW72vYJQAi33QmK1kotGA.jpg

stellite and v7 go up 20HR per card if use 1.6.1 driver but tube not work with HBC mem,.

[RuMiner]

I have 4 VEGA 56 (3 ref & 1 peace of sh..)
I was at 7500-7520h/s  and now  I'm at 7620-7630h/s with the same "summer" profile (CC:1340Mhz / MC:900Mhz)

that doubling trick doesn't work for me, but I have 7920-7925 h/s without it on 4 vega56 (ref or noname idk, it was OEM and the only sign on it is RADEON), cc 1450-1470, mc 925-935 (found exact stable maximum for each card).

[Vince34]

I have 4 VEGA 56 (3 ref & 1 peace of sh..)
I was at 7500-7520h/s  and now  I'm at 7620-7630h/s with the same "summer" profile (CC:1340Mhz / MC:900Mhz)

that doubling trick doesn't work for me, but I have 7920-7925 h/s without it on 4 vega56 (ref or noname idk, it was OEM and the only sign on it is RADEON), cc 1450-1470, mc 925-935 (found exact stable maximum for each card).

I don't know wether the trick works or not and I don't care, +20h/s? no big deal! 
BTW, if you have only RADEON written on your vegas, you have ref cards
My non ref card (hynix memory) runs stable at 1775 with higher consumption 
My 3 ref cards (samsung memory) go over 2000h/s with CC:1407 / MC:941 but run too hot so I lower the frequencies during the summer

[doktor83]

The trick is working on "v7" algos, on heavy, tube, haven nope 

[dragonmike]

I've got a question about the reboot script when using pool switching: do you have to set it for each algo separately or can you just add it at the end of the start.bat command line?

...Doc?

[doktor83]

I've got a question about the reboot script when using pool switching: do you have to set it for each algo separately or can you just add it at the end of the start.bat command line?

...Doc?

reboot script is the one you add in config.txt, so yes, add it in every config.
That is handy because maybe your heavy algo clock settings in overdriventool are not the same as for v7, so on every algo start it will run the appropriate batch file.