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

[doktor83]

Hi guys. Use srb 1_6_9 on my 7970 and have a less hashrate compared to 1_6_8. The problem is that the value of "fragments"  does not change, it is always 4. Heres my config.txt:
{
"cryptonight_type" : "normalv8",
"intensity" : 57,
"worksize" : 16,
"double_threads" : false,
"fragments" : 8
}


Where is my mistake? Thank you.

You can't define fragments there.
Do it like this :

Code:

"gpu_conf" : 
[ 
	{ "id" : 0, "intensity" : 57, "worksize" : 16, "threads" : 2, "fragments" : 8}
]

Thank you, now it works. As i understand value of fragments can be equal only to this values:0,1,2,4,8,16,32,64,128 ?

Yes, that's right.

You said you have less hashrate with 169 compared to 168. Is that what the exact same settings?
What numbers were you getting on 168, and now on 169 ?

[playfast]

Doktor, kudos on your fabulous miner and keep up the great work!
Question, is there a way to see which particular GPU found results/shares?

[nordmann666]

is there a more detailed log level possible?

miner stops mining until i see that there is no action since many minutes...have to press key and than i got error messages with many invalid shares following

[dingdongtobias]

is there a more detailed log level possible?

miner stops mining until i see that there is no action since many minutes...have to press key and than i got error messages with many invalid shares following

if win10 don't click in the miner window that halt miner execution, you have that problem 100%

[nordmann666]

is there a more detailed log level possible?

miner stops mining until i see that there is no action since many minutes...have to press key and than i got error messages with many invalid shares following

if win10 don't click in the miner window that halt miner execution, you have that problem 100%

it stopps without clicking in the cmd - and i disabled quick edit mode

[jazz1984]

Hi guys. Use srb 1_6_9 on my 7970 and have a less hashrate compared to 1_6_8. The problem is that the value of "fragments"  does not change, it is always 4. Heres my config.txt:
{
"cryptonight_type" : "normalv8",
"intensity" : 57,
"worksize" : 16,
"double_threads" : false,
"fragments" : 8
}


Where is my mistake? Thank you.

You can't define fragments there.
Do it like this :

Code:

"gpu_conf" : 
[ 
	{ "id" : 0, "intensity" : 57, "worksize" : 16, "threads" : 2, "fragments" : 8}
]

Thank you, now it works. As i understand value of fragments can be equal only to this values:0,1,2,4,8,16,32,64,128 ?

Yes, that's right.

You said you have less hashrate with 169 compared to 168. Is that what the exact same settings?
What numbers were you getting on 168, and now on 169 ?

Last stable results on v8 was 470-475 H/s. Driver 18.6.1, win 7 x64, srbminer_1_6_8 intencity 57, worksize 16, no doublethreads. Clocks 1100 core / 1500 memory.

With Srb_1_6_9 with same settings and drivers (only new version of miner) i got 465 H/s. The only i change the value of fragments. 1,2 shows very low hashrates 150-250, and the best for my card is "fragments" :16.

[UAGet]

RX 560 2Gb
1.6.8 - 526 h/s
1.6.9 - 490 h/s 

[doktor83]

RX 560 2Gb
1.6.8 - 526 h/s
1.6.9 - 490 h/s 

have no fear, just report here 

Anyone with 4gb 560 can report a change in hashrate?
I have only 4gb card and there nothing changed from 168->169 when testing.

[digitalunix]

doktor83 Maybe SRBMiner mining cryptonight-webchain soon?

[Kgonla]

RX 560 2Gb
1.6.8 - 526 h/s
1.6.9 - 490 h/s 

have no fear, just report here 

Anyone with 4gb 560 can report a change in hashrate?
I have only 4gb card and there nothing changed from 168->169 when testing.

You changed something that makes 8gb cards to do better hash rate but worst for 4gb & below, at least in some cases.

[Uaciuganadu]

V1.6.9
- Algo switching without miner restart
- Benchmark everything from algos.txt and just paste the hashrates (--benchmarkalgos)
- Added number of algo switches to API and stats
- Added cmd parameter --resetmineronalgoswitch which forces miner to reset on algo change
- Changed minimum --algoswitchmintime from 3 min to 30 sec, default is still 600 sec
- Fixed API pool stats when not connected to a pool
- Added cmd parameters --cjobtimeout, --cmaxdifficulty, --ckeepalive
- When critical temp is reached, ADL temp is now logged before shutdown
- Notification on too many compute errors (set with --gpuerrorsalert value)
- Added a performance tuning parameter 'fragments' for gpu_conf and cmd
- Fixed a bug that could crash miner on shutdown


+ Algo switch without miner restart is here finally. This is now the default mode. If you want to use the 'old fashioned' switch where the miner restarts itself use --resetmineronalgoswitch in .bat.
The only reason i can see to use the switching with restart is for Vegas, because they tend to drop hashrate on algo switch, and only --resetvega can help to regain full speed again.
Check out here how to setup algo switching

+ Some people were too lazy to benchmark algo by algo to get the 'hashrate' values for algos.txt, so there is a --benchmarkalgos now , that benchmarks the algos set in algos.txt, and creates benchmark_results.txt, from where you just have to take and paste the values into algos.txt

+ The --algoswitchmintime minimum value can now be 30 seconds, altough Monero Ocean really likes to disregard this setting

+ There is on-screen and log notification now when you have too much compute errors (default is 15). You can set this value with --gpuerrorsalert value

+ (re)added fragments parameter for some performance tuning. This parameter was set internally, but my tests show it can REALLY be different for even the same type of GPU, but different vendor.
So now everyone can find his 'optimal' value for this parameter. It differs for algos and also for the amount of VRAM, so a value that is good for 4GB cards maybe isn't the best value for 8GB cards.

Hey Dok,

Indeed on Vega the miner kinda brakes and can not handle the change without --resetmineronalgoswitch . This also affects the --benchmarkalgos as the function ignores the --resetmineronalgoswitch in my tests.

Is there a way for the above to get fixed or make the reset of the miner faster? Also can you make it so that the bench performs the restart?

[goran89]

RX 560 2Gb
1.6.8 - 526 h/s
1.6.9 - 490 h/s 

have no fear, just report here 

Anyone with 4gb 560 can report a change in hashrate?
I have only 4gb card and there nothing changed from 168->169 when testing.

You changed something that makes 8gb cards to do better hash rate but worst for 4gb & below, at least in some cases.

I have better hashrate on 4 gb cards with 1.6.9 on all algos.
3x RX570+ 2x RX 580 = 15 more hashes on v8
                                    35 more hashes on v7
                                    100 more hashes on fast

[abg00]

RX 560 2Gb
1.6.8 - 526 h/s
1.6.9 - 490 h/s  

have no fear, just report here  

Anyone with 4gb 560 can report a change in hashrate?
I have only 4gb card and there nothing changed from 168->169 when testing.

1.6.9 v8
560\2gb 465 h\s
560\4gb 470 h\s
550\4gb 403 h\s
550\2gb 380 h\s

470\570\4gb with auto int=58 930 h\s
470\570\4gb with int=57 942 h\s

1.6.9 heavy
560\4gb 530 h\s !!!!

[ivomm]

What are your intensity for 560 cards?

[abg00]

What are your intensity for 560 cards?

v8
26 for 2gb
50 for 4gb

heavy
27 for 4gb

[playfast]

Best bralock setting is 6 for my rx560 2gb cards, only 2-4 H/s gain though. I noticed while testing bralock, it prefers even numbers.
Funny thing is, on Claymore's ETH miner, the best setting was also 6 for dcri tuning, makes me wonder if bralock is the Cryptonight equivalent or something.

[livada]

srb 1.6.9 give more HR than 1.6.8 . +30HR per vega 56 referent card on V7-XTL

[GKumaran]

SRBMiner : 1.6.9
Driver : 18.6.1
Algorithm : CN-LightV7
Card : Vega 64

Does anyone else have this issue? or knows how to solve it?
Running 6 vega 64, the clocks are stable and tested speeds.

But once mining starts, after 30 min one card drops from 4500h/s to 4100h/s
Then after 2hours, another card drops from 4500h/s to 4100h/s

This continues till all cards drop to 4100h/s, how to prevent these hash drops?
Lowering intensity, clock speed also results in the same drops.

[BogdanCo]

SRBMiner : 1.6.9
Driver : 18.6.1
Algorithm : CN-LightV7
Card : Vega 64

Does anyone else have this issue? or knows how to solve it?
Running 6 vega 64, the clocks are stable and tested speeds.

But once mining starts, after 30 min one card drops from 4500h/s to 4100h/s
Then after 2hours, another card drops from 4500h/s to 4100h/s

This continues till all cards drop to 4100h/s, how to prevent these hash drops?
Lowering intensity, clock speed also results in the same drops.

Check your power and sleep settings from windows. Switch screen and sleep to "never" if you have them on.  

[GKumaran]

It is already set to never. BTW the display is on IGPU.