Re: [Jack-Devel] jack dsp load calculation

On Sat, Dec 26, 2015 at 3:04 PM, Robin Gareus <[hidden]> wrote:

> > For what it's worth, Radium reports three values: 1. Minimum CPU measured
> > for a block during the last second, 2. Average CPU usage during the last
> > second,
> > 3. Maximum CPU usage measured for a block during the last second
> > ( http://folk.uio.no/ksvalast/radiumcpu.png )
>
> nice.
>
> That is per application, right?  Not the whole system - jack can include
> other clients.
>
>
Yes, this is just local CPU measures. No jack calls.


> All three values are useful, at least for me as a developer of the
> program,
> > but I guess the users might find all three values interesting as well.
>
> For end users in Mixbus  we are considering to maybe even "dumb it
> down": A simple light: green/yellow/red or a short e.g 6-LED peak-meter.
>
> The motivation here: don't encourage comparing percent values.
>
> However it must be meaningful to answer
>  1) can I safely add more plugins?
>  2) can I lower the period-size or is the current cycle already very
> short for my setup?
>
>
Guess it could be complicated to do that without showing accurate values to
the user.
As a user, I would also wonder why I am not allowed to see percentages.



> One thing I'm not quite sure of, which is always apparent because all the
> > values are visible, is why there is such a large difference between
> > minimum and maximum CPU usage. It's usually at least 4-10
> > percentage points. I hope it's because of measurement
> > errors.
>
> On which platform is that? with JACK?
>
>
Just calling clock_gettime(CLOCK_MONOTONIC, &time) before and
after processing audio locally in Radium. CPU numbers from jack is
not shown in Radium.

1451146307.4907_0.ltw:2,a <CAC6niELMYg6rnkMZR_4CVODKSCxZ1pULQNfREUmz9=SvnUjW4w at mail dot gmail dot com>