> Also, it would be better to have a workaround for this. Perhaps we > could simply make the default value of max nonzero? In the old > throttling code the slice time is 0.1s, so perhaps we could see what > happens with max=0.1*avg.
This gives correct results with cfg with some little auto compensated oscillations. I will definitelly drop the bogus comment. Best regards Benoît
