Re: [Jack-Devel] Interpreting 'Clients end date' gnuplot diagram

I did new tests in both synchronous and asynchronous modes.
I uploaded all the results:

   [Asynchonous]
Audio driver timing:
http://denes.rudanium.org/shots/perform-2-audiodrivertiming.png

Clients duration:
http://denes.rudanium.org/shots/perform-2-clientsduration.png

Clients end date:
http://denes.rudanium.org/shots/perform-2-clientsenddate.png

Driver end date:
http://denes.rudanium.org/shots/perform-2-driverenddate.png

Scheduling latency:
http://denes.rudanium.org/shots/perform-2-schedulinglatency.png

   [Synchronous]
Audio driver timing:
http://denes.rudanium.org/shots/perform-3S-audiodrivertiming.png

Clients duration:
http://denes.rudanium.org/shots/perform-3S-clientsduration.png

Clients end date:
http://denes.rudanium.org/shots/perform-3S-clientsenddate.png

Driver end date:
http://denes.rudanium.org/shots/perform-3S-driverenddate.png

Scheduling latency:
http://denes.rudanium.org/shots/perform-3S-schedulinglatency.png

In synchrnous mode, it works nicely without xruns. But the audio
driver timing looks really ugly and that can't be good in general.
It is an onboard soundcard, I don't expect wonders to happen but
if you have any hints on improving the situation, I would be very
glad to hear them.

Also, there is an interesting spike at around the 20000th cycle
in asynchrnous clients duration and scheduling latency. A possible
cause is my automatic process shielding script which checks running
processes every 20 seconds for my client and puts it on two exclusive
cores with jack. I could imagine that this "switch" can cause a spike
in scheduling.

Thank you for your help,
Dennis

On 2012-03-18 16:00, Stéphane Letz wrote:
> The audio interrupt indeed seems suspicious.  Can you put other
> diagrams on your site?
>
> You can also try jackd in "synchronous" mode like:
>
> jackd -S -P83 -dalsa -dhw:0 -r48000 -p64 -n3 -Xraw
>
> Stéphane
>

1332085054.26405_0.ltw:2,a <27bd7dbf5899faf49f1d7274228a6e07 at rudanium dot org>