do you mean difficulty should be mapped to a smaller range such that it's easier to read? Float is a datatype representing real numbers it's not related to the radix/base that's used for representation.
What I mean is that pools expect difficulty configuration as a number, so even I know where my performance sweet spot is - I cannot just paste it as a hint to the pool.
I am not sure if that is possible, but it would be appreciated.
- Current log makes little sense without further tools. (I would appreciate more details)
What details are you missing? And how is it related to tools you would not need otherwise?
The idea of logging change is to make it easier to spot problems. The log right now has the information you need, it is just clumped together.
For example I switched to mining pool hub and performance dropped 5-10% - I used python to split the information and found out they are seemingly randomly changing difficulty back to 0001....
I checked the shares and found out the coin switching is not nicely implemented by the pool.
Other card had performance problems due to fan not scaling (For some reason the fan speed was not scaled on temperature in 2D mode).
- Here might be a good innovation. If you can read PerfCap Reason and accordingly to it would be better rather than temperature.
- I suspect targeting a temperature will be a good workaround
Now I am trying to find sweet spots for Sol/W, because going as fast as possible is not always the best efficiency.
Anyway I am looking forward to new versions, but I am sticking with 0.5.7. Performance on 0.5.8 is worse for me CPU wise.
Now that's is a very useful information. If there are any regressions between the versions - pls report them - I can't fix them otherwise and they might appear in later versions too. How much did the cpu load increase for you?
Since you took the time to respond, I took the time to replicate my original problem.
Unfortunately I was not able to. I am now running at 0.5.8