On Fri, Mar 11, 2016, at 07:13 PM, Fons Adriaensen wrote:
A client that generates a very uneven load (e.g.
doing big FFTs every Nth cycle) can easily make it indicate
much more than the average CPU load. Of course clients doing
that are just badly implemented, but they do exist.
Badly implemented? For a convolver perhaps, but I think (as I would)
that it's perfectly fair to implement some methods that way. A phase
vocoder at a short period size will exhibit exactly that behaviour.
Chris