Re: [Jack-Devel] jack dsp load calculation

On Sun, 27 Dec 2015 10:34:26 +0000
John Emmas <[hidden]> wrote:

> On 26 Dec 2015, at 23:05, Robin Gareus wrote:
> 
> > On 12/26/2015 10:56 PM, Joakim Hernberg wrote:
> > [..]
> >   
> >> IME the dsp load is a relatively useless measure as it's not really
> >> related to the max value (which is where an xrun occurs)..  You
> >> could very well have a system with a very low dsp load xrunning
> >> all the time...  
> > 
> > exactly.
> >   
> 
> No, not quite...  you can have a system "displaying" a very low DSP
> load even though it's xrunning all the time.  But that problem is NOT
> caused by Jack's CPU load calculation.  Nor is it caused by the
> averaging strategy.

I'd agree with this.  The measures are separate, and it's useful to
know approximately how much headroom you have left until exceeding the
deadline.  Not really related to xruns at all, until you start
exceeding a certain threshold.  Still it would be very useful to have
an indication of the max latency reached so far and not only an
average.  Personally I've been missing this for a long time.  I'd think
the best solution would be the addition of a new call that returns,
max, min and some kind of average of the graph's execution latency.

-- 

   Joakim

1451259089.5565_0.ltw:2,a <20151227181508.4007c657 at balder dot valhalla dot alchemy dot lu>