24 May
2016
24 May
'16
2:31 p.m.
hi Linux audio community!
i've been strugling with XRUNS and glitches on a machine using Renoise,
SuperCollider and Processing. i wrote a question also on Renoise forum,
but everything boils down to this:
Renoise seems to be running some threads with FIFO scheduler with a
priority that is _below_ that of JACK and firewire driver (correct
right?), but ALSO some threads using Round Robin scheduler with VERY
HIGH RT priority of 95. my question is if this is a possible cause for
glitches and XRUNS? the priority of 95 is above realtime clock (RTC)
and firewire irq! i wonder if Round Robin scheduler isn't somewhat less
stressful for the system and FIFO threads would still have priority?
PRI RTPRIO CLS PID NI CMD
135 95 RR 2255 - renoise
135 95 RR 2255 - renoise
130 90 FF 114 - [irq/8-rtc0]
125 85 FF 200 - [irq/20-firewire]
106 66 FF 2583 - jackd -R -P 60 -d firewire -r 44100 -p 128 -n 3
so i'm asking Renoise guys if they know anything about it.
to test, is there a way to start a process and force to use different
scheduler AND/OR change priority?
chrt reports Renoise is using SCHED_OTHER.
any ideas greatly appreciated.
the full forum post (with more data) is here:
http://forum.renoise.com/index.php/topic/47767-linux-priority-too-high/
best,
Luka
--
Luka Prinčič / Nova deViator // + 386-40-66-77-98 / http://deviator.si /
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
27·may Interface Fractures III:SILICON | In/Visible Cities, Gorizia, IT
31·may Turns Me On EP & VIDEO release | http://patreon.com/novadeviator
01·jun Koordinate Zvoka | Pritličje | Ljubljana·SI
· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · ·
OUT NOW!
*Wanda & Nova deViator: Recursion EP (free DL & video)*
http://wndv.bandcamp.com/album/recursion-ep
https://youtu.be/4D2cTyAmj0k
· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · ·
MORE MUSIC: http://novadeviator.bandcamp.com
SUBSCRIBE: http://nova.deviator.si/follow
PATREON: http://patreon.com/novadeviator
MORE: http://wndv.si | http://kamizdat.si | http://emanat.si
· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · ·
gpg key: http://pgp.mit.edu/pks/lookup?op=get&search=0x1397C721FFA52FD7
· ·
The great moral question of the twenty-first century is this:
if all knowledge, all culture, all art, all useful information can be
costlessly given to everyone at the same price that it is given to
anyone; if everyone can have everything, anywhere, all the time,
why is it ever moral to exclude anyone?
-- Eben Moglen
- -
24 May
24 May
2:42 p.m.
On Tue, 24 May 2016 14:31:37 +0200, Luka Prinčič / Nova deViator wrote:
135 95 RR 2255 - renoise
135 95 RR 2255 - renoise
130 90 FF 114 - [irq/8-rtc0]
125 85 FF 200 - [irq/20-firewire]
I guess rtc is unimportant nowadays, but the sound card should get a
higher priority. On my installs the sound cards always have the highest
priority.
[rocketmouse@archlinux ~]$ rtirq status | head -n5
PID CLS RTPRIO NI PRI %CPU STAT COMMAND
299 FF 90 - 130 0.0 S irq/18-snd_hdsp
27 FF 50 - 90 0.0 S irq/9-acpi
41 FF 50 - 90 0.0 S irq/8-rtc0
3:19 p.m.
Hello Luka,
i've been strugling with XRUNS and glitches on a
machine using Renoise,
SuperCollider and Processing. i wrote a question also on Renoise forum,
but everything boils down to this:
Renoise seems to be running some threads with FIFO scheduler with a
priority that is _below_ that of JACK and firewire driver (correct
right?), but ALSO some threads using Round Robin scheduler with VERY
HIGH RT priority of 95.
Do you have any idea where this is being set? Or what is setting this?
my question is if this is a possible cause for
glitches and XRUNS? the priority of 95 is above
realtime clock (RTC)
and firewire irq!
If Renoise is using a lot of CPU cycles I reckon it could preempt other
processes with a lower rtprio. But I'm not a Renoise user and I don't
know the specs of your workstation.
i wonder if Round Robin scheduler isn't somewhat less
stressful for the system and FIFO threads would still
have priority?
Afaik it's the rtprio that counts, not the scheduler. The scheduler only
matters if processes have the same rtprio, in that case SCHED_FIFO
processes apparently do not preempt SCHED_RR ones.
PRI RTPRIO CLS PID NI CMD
135 95 RR 2255 - renoise
135 95 RR 2255 - renoise
130 90 FF 114 - [irq/8-rtc0]
125 85 FF 200 - [irq/20-firewire]
106 66 FF 2583 - jackd -R -P 60 -d firewire -r 44100 -p 128 -n 3
so i'm asking Renoise guys if they know anything about it.
to test, is there a way to start a process and force to use different
scheduler AND/OR change priority?
Yes, you can do that with chrt:
chrt -f -p 2255 80
This will set the scheduler to SCHED_FIFO for pid 2255 and sets rtprio
80 for it.
Jeremy
3:47 p.m.
On Tue, 24 May 2016 14:31:37 +0200
Luka Prinčič / Nova deViator <nova(a)deviator.si> wrote:
to test, is there a way to start a process and force
to use different
scheduler AND/OR change priority?
Another cool utility (gui) to change scheduling class and priority is
tuna. IMO excellent for messing around with stuff like this.
--
Joakim
3158
days inactive
3158
days old
linux-audio-user@lists.linuxaudio.org
3 comments
4 participants
participants (4)
-
Jeremy Jongepier -
Joakim Hernberg -
Luka Prinčič / Nova deViator -
Ralf Mardorf