dok did you receive the heavy algo changes from devs?

I found interesting thing...
As we know 1.5.8 creats srb files every launch... But names of this files differes (they even have different file size) every time. I make suggestion that different speed at mining connected with these different kernels. To achive max mining speed I relaunched 1.5.8 miner many times until it gives me max speed.

1.5.9 version creates srb files only if them absent. But I tried many times relaunch miner with deletion of srb or on the same kernel file. But I can't get max speed... Maybe I just unlucky, or maybe 1.5.9 can't compile best kernel...

After I make next steps:
1. Roll back to 1.5.8. Relaunched them until it gives max speed. Copied last created srb file into backup safe place.
2. Installed 1.5.9. Launched them once to recieve srb file in cache dir.
3. Close miner. Replaced srb file in cache dir from 1.5.9 by srb file created on 1.5.8 giving max speed with the name from file 1.5.9.
4. Voila! Now 1.5.9 have quick launch without recreating srb file and gives max speed everey launch (I hope - I just tries several times).

This can help peoples who have troubles with unstable max speed.

doctor, can it be that 1.5.9 miner can't compile best kernel due to driver issuies or something else?

pls give me comand to start NH i try but  alvay error.
Where i write this?
"nicehash" : true, - i write this in config but error.

I write  this in pool and agan error .
   {"pool_use_tls" : false, "pool" : "cryptonightv7.eu.nicehash.com:3363", "wallet" : "address", "password" : "x", "max_difficulty" : 1500000}, for 6 vega

Bro, in my case, after reconnecting, the hashrate was drop. But after waiting a few minutes, it's back normal.
May be you were too quick to observe?

unbelievable but true. my RX 550 2gb at 1.5.8 gave out stably 6590 hashes at setting 26/8/2, and on 1.5.9 neither as more than 6510 hashes

Cool stuff, dok. Starting to move to 1.5.9 now, 5 left remaining  .

yeah dok im sticking to 1.5.8 my vegas got higher output compared to 1.5.9. https://www.reddit.com/r/havenprotocol/comments/8ohw6t/haven_v3_hardfork_coming_in_2_weeks/ - haven is also forking.
https://www.reddit.com/r/stellite/comments/8p1tss/v4_mandatory_update_for_all_node_maintainers_of/ - stellite too

wow many thanks dok, will try now mining on nicehash with max_difficulty.

Great update, good thinking on devfee pool settings, although a hardcoded fallback in code would still be beneficial.

Doktor, how costly is algo change? I'm working on a simple coin switching proxy (forked from a sebseb7's repository of cryptonote-proxy) which works well for same algo coins. The upside is there's no hasrate drop between changes as SRBMiner (or any other miner connected to it) just sees it as a new job.

That said, just as GPU's can run several different shaders, how hard would it be to change algo without a restart? Memory would be reserved for the one with the most mem requirements. It would be awesomely dandy if SRB could do this, it would support an extra json property to change algos in the job request.

much appreciated, gotta try this out. just updated to 1.5.8 recently but i noticed after a few days the miner would just suddenly stop, hopefully its fixed! will update tonight

Any hashrate increase? Like for 1.5.8. when you didn´t say anything and my vegas hashed like 200 more per rig, what a nice surprise 

Done, buddy. Thanks for your awesome work. All my AMD rigs (and my friends') are sporting your miner.

I confirm a strange hashrate drop on 18.5.2 with CN7, although it starts from a better result. E.g. 8 x Vega64 gave ~14000 on 18.4.1, now it runs at ~14200, but sevaral hours later it can drop to 13700. Miner restart helps. And it is definitely not  throttling or overheating, because they are liquid cooled edition and don't raise above 50C. Rolled one rig back to 18.4.1.

driver version?
reinstall driver with cleanup

samo da znas da ti nesto ne valja s poolom za devfee.
verzija je zadnja 1.5.8 a rurdario sam NBR

It is exactly after 2 Hours, every time and it is not for short time, it drops for ever until I restart SRBminer.
Anyway, if you are sure it is not related to DevFee, then it is something what happens about that timeframe.

I don't know is that bug from miner or from driver...
I noticed that if I restart miner many times (one of methods to achieve max speed) my amount of RAM decreases in time... When it's start to grow my pagefile.sys file to 35Gb I decided to find - where is memory leak... No one process didn't use so many RAM (I have 12Gb RAM and 24Gb pagefile size).
1st i didn't find who eat my memory, and just restart computer to stop that.

Than I start to remember - after what it start, and I remembered that it starts after I start to use SRB miner...

After I run GPU-Z and didn't believe my eyes! GPU-Z shows on both of my RX 580 8Gb cards used video memory 14Gb on 1 card and 15Gb on 2nd! I don't know how it can be, but after closing miner, used vmemory on cards decreased to 7Gb and 7,5Gb. GPU chips usage is 0%, but vmemory is used!

I start to run and close miner, and I notice that after each closing used vmemory on idle cards grows... During GGS and Claymore usage I didn't have this problem...

doctor, check please releasing video memory on closing miner. I suspect that it doesn't releases them all...