More on the OC topic.
if you are profit mining, and the miner dies, and AM restarts it. it seems the *stop* OC is sent, but the *start* is not. Happens in all cases on all miners.
I'll have to go look at the long the next time it happens, but my guess is because its trying to restart the algo that had just killed the miner if may think it doesn't need to execute it, because it did that already - just a though.
It's possible to follow all the GPU clocking commands that Awesome Miner send to MSI Afterburner if you search for "Executing GPU clocking command" in the Remote Agent log file. You can that verify exactly which commands that are being sent and when. Please get back to me if you find any issues.
In general, if Awesome Miner restarts a crashed mining process, it will apply the Start-clocking profile again.
Hi Patrik,
Can confirm I'm also experiencing clocking profile execution issue, I haven't used the feature much, just trialling to see if it works out. I'm getting similar issues where the starting profile doesn't get applied when profit switching took place. Not just if miner crashed, as @akadamson said though, the stop seems always executed, but not the start. I'll try to see if I can spot it in the logs and send you a copy.
Just FYI, after seeing the behavior, I bulk removed the clocking profiles from the profit profile then manually load the desired clocking again via AM. Then strangest thing is AM still send the stopping profile (which was unchecked) command to the remote rig upon profit switching.
Maybe it's something with the sequence of execution of commands gets complex during profit switching, timeouts between running processes (ab, remote agent, mining SW, ab remote server...etc) especially rig is running tight on CPU resources with 8 gpu and a cheap Celeron, CPU is always 80-100% when mining process is running, that's just a guess