Lowering of frequency with auto avalon is a result of it trying to maintain a certain temperature as well, yes?
What would be the conclusion if a particular machine hashes at over 80, but slowly declines to the mid 70s lowering frequency? Lack of adequate cooling?
FYI: Aside: The GH/s reported by the avalon code is not the device hash rate, it is the 1diff share find rate.
Thus it will also change with luck.
But the pool shows sustained lowering of submitted shares, the device seems to agree, and the MHashes are lowering. You are saying that even if it said hashing 3ghash, that's not the "actual hash rate"? Where can I find accurate data on the machine then? Or maybe I misunderstood your reply.
With an avalon - the 'actual' hash rate is not available.
The hardware is ... for want of a better word ... "difficult" to determine the actual hash rate.
(maybe a better word is "crap")
Yes if the pool is indeed showing a generally decreasing hash rate over short interval measurements, then your device is slowing down.
However, of course, short interval measurements are also unreliable and affected by luck, so you would need a definite clear reduction over many samples over that time period to be sure it was systematic and not luck.
However, my point is that the screen average (or API "MHS av") will be affected by "luck"
and the higher your work difficulty, the more obvious that effect will be.It may or may not be the case for your observations, but it's just that there is more than one possibility.