Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 113. (Read 237247 times)

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.

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.

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

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.

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

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

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 ?

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

What is your hash rate for the 7970? What is the clock speed?

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.

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.

write algo
write config

no mindreaders!

Hi everybody,
How to fix compute errors?
Thanks