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

[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.

[1576424960]

1576424960

[1576424960]

1576424960

[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.

[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?

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.

Cheers - done.
Let's see how the rigs behave overnight!


EDIT: still also possible to set a logfile?
EDIT 2: Should "fast" and "stellitev4" be using the same clocks and settings generally as "normalv7" (on Vega and RX 570's)?

[Mashy81]

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.

Cheers - done.
Let's see how the rigs behave overnight!


EDIT: still also possible to set a logfile?
EDIT 2: Should "fast" and "stellitev4" be using the same clocks and settings generally as "normalv7" (on Vega and RX 570's)?

I normally run the same clocks and settings. I only change mine for heavy and lite

[zeef]

Hi doktor,

I was using version 1.6.3 in my vega 56,

using the 1.6.6 i got less 30 hs

Using same settings,

On other rigs with rx 580 and vega 64 got the same hashes.

Just reporting 

[ikyo]

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

Any extra hash rate you can get is a great thing.  It isn't that much per card, but if you have multiple it does add up.

[duyquang06]

Hi doktor,

I was using version 1.6.3 in my vega 56,

using the 1.6.6 i got less 30 hs

Using same settings,

On other rigs with rx 580 and vega 64 got the same hashes.

Just reporting 

Tell him which driver you using.

[doktor83]

Hi doktor,

I was using version 1.6.3 in my vega 56,

using the 1.6.6 i got less 30 hs

Using same settings,

On other rigs with rx 580 and vega 64 got the same hashes.

Just reporting 

Tell him which driver you using.

and which algo is it 

[wgestickley]

Good Morning,

i have trouble to run 2 different instances of SRB Miner with the new Algo Switching Option.
While i have a rig with 5xRX570 and 1XRX580, i want to run the Miner bundeld for the Cards. So 1X with the 570ies and 1X with the RX580.

The GPU ID for the 580 is 3 and i put this in the start.bat

SRBMiner-CN.exe --config config-fast.txt --cgpuid 3 --cgpuintensity 60.5 --cgputhreads 2 --pools pools-algoswitch.txt --sendallstales --usealgoswitching

The Miner closes instently after start. When i dont exclude any GPU (all 6 togehter) it runs fine....

Thank you

[doktor83]

Good Morning,

i have trouble to run 2 different instances of SRB Miner with the new Algo Switching Option.
While i have a rig with 5xRX570 and 1XRX580, i want to run the Miner bundeld for the Cards. So 1X with the 570ies and 1X with the RX580.

The GPU ID for the 580 is 3 and i put this in the start.bat

SRBMiner-CN.exe --config config-fast.txt --cgpuid 3 --cgpuintensity 60.5 --cgputhreads 2 --pools pools-algoswitch.txt --sendallstales --usealgoswitching

The Miner closes instently after start. When i dont exclude any GPU (all 6 togehter) it runs fine....

Thank you

put pause after the SRBMiner-CN.exe --config config-fast.txt... line so the window wont close on error, and you can see what is the error, like this :

SRBMiner-CN.exe --config config-fast.txt --cgpuid 3 --cgpuintensity 60.5 --cgputhreads 2 --pools pools-algoswitch.txt --sendallstales --usealgoswitching
pause

[wgestickley]

Good Morning,

i have trouble to run 2 different instances of SRB Miner with the new Algo Switching Option.
While i have a rig with 5xRX570 and 1XRX580, i want to run the Miner bundeld for the Cards. So 1X with the 570ies and 1X with the RX580.

The GPU ID for the 580 is 3 and i put this in the start.bat

SRBMiner-CN.exe --config config-fast.txt --cgpuid 3 --cgpuintensity 60.5 --cgputhreads 2 --pools pools-algoswitch.txt --sendallstales --usealgoswitching

The Miner closes instently after start. When i dont exclude any GPU (all 6 togehter) it runs fine....

Thank you

put pause after the SRBMiner-CN.exe --config config-fast.txt... line so the window wont close on error, and you can see what is the error, like this :

SRBMiner-CN.exe --config config-fast.txt --cgpuid 3 --cgpuintensity 60.5 --cgputhreads 2 --pools pools-algoswitch.txt --sendallstales --usealgoswitching
pause

ccryptonighttype valid values:
[normal, normalv7, lite, litev7, heavy, bittubev2, artocash, alloy, marketcash, b2n, stellitev4, haven, fast, italo, mox]
Drücken Sie eine beliebige Taste . . .

***

And my config-fast.txt is like this

{
"cryptonight_type" : "fast",
"target_temperature" : 64,
"intensity" : 59,
"double_threads" : true
}

[doktor83]

Good Morning,

i have trouble to run 2 different instances of SRB Miner with the new Algo Switching Option.
While i have a rig with 5xRX570 and 1XRX580, i want to run the Miner bundeld for the Cards. So 1X with the 570ies and 1X with the RX580.

The GPU ID for the 580 is 3 and i put this in the start.bat

SRBMiner-CN.exe --config config-fast.txt --cgpuid 3 --cgpuintensity 60.5 --cgputhreads 2 --pools pools-algoswitch.txt --sendallstales --usealgoswitching

The Miner closes instently after start. When i dont exclude any GPU (all 6 togehter) it runs fine....

Thank you

put pause after the SRBMiner-CN.exe --config config-fast.txt... line so the window wont close on error, and you can see what is the error, like this :

SRBMiner-CN.exe --config config-fast.txt --cgpuid 3 --cgpuintensity 60.5 --cgputhreads 2 --pools pools-algoswitch.txt --sendallstales --usealgoswitching
pause

ccryptonighttype valid values:
[normal, normalv7, lite, litev7, heavy, bittubev2, artocash, alloy, marketcash, b2n, stellitev4, haven, fast, italo, mox]
Drücken Sie eine beliebige Taste . . .

***

And my config-fast.txt is like this

{
"cryptonight_type" : "fast",
"target_temperature" : 64,
"intensity" : 59,
"double_threads" : true
}

Make it look like this :

SRBMiner-CN.exe --ccryptonighttype fast --config config-fast.txt --cgpuid 3 --cgpuintensity 60.5 --cgputhreads 2 --pools pools-algoswitch.txt --sendallstales --usealgoswitching

And now it will use intensity 60.5 instead of 59 you defined in config.
CMD parameters are always "stronger" than the ones in config file.

[wgestickley]

Good Morning,

i have trouble to run 2 different instances of SRB Miner with the new Algo Switching Option.
While i have a rig with 5xRX570 and 1XRX580, i want to run the Miner bundeld for the Cards. So 1X with the 570ies and 1X with the RX580.

The GPU ID for the 580 is 3 and i put this in the start.bat

SRBMiner-CN.exe --config config-fast.txt --cgpuid 3 --cgpuintensity 60.5 --cgputhreads 2 --pools pools-algoswitch.txt --sendallstales --usealgoswitching

The Miner closes instently after start. When i dont exclude any GPU (all 6 togehter) it runs fine....

Thank you

put pause after the SRBMiner-CN.exe --config config-fast.txt... line so the window wont close on error, and you can see what is the error, like this :

SRBMiner-CN.exe --config config-fast.txt --cgpuid 3 --cgpuintensity 60.5 --cgputhreads 2 --pools pools-algoswitch.txt --sendallstales --usealgoswitching
pause

ccryptonighttype valid values:
[normal, normalv7, lite, litev7, heavy, bittubev2, artocash, alloy, marketcash, b2n, stellitev4, haven, fast, italo, mox]
Drücken Sie eine beliebige Taste . . .

***

And my config-fast.txt is like this

{
"cryptonight_type" : "fast",
"target_temperature" : 64,
"intensity" : 59,
"double_threads" : true
}

Make it look like this :

SRBMiner-CN.exe --ccryptonighttype fast --config config-fast.txt --cgpuid 3 --cgpuintensity 60.5 --cgputhreads 2 --pools pools-algoswitch.txt --sendallstales --usealgoswitching

And now it will use intensity 60.5 instead of 59 you defined in config.
CMD parameters are always "stronger" than the ones in config file.

Now he detects only this 1 specified GPU... BUT :-)

Pool send a new job for bittubev2, he starts initializing it and is in an endless loop of initializing betwen fast and bittubev2....

Hmmmm....