9 Aug
2016
9 Aug
'16
3:41 p.m.
Hey hey everyone,
for a few months now my jackd1 (0.121.3) takes on a lot of CPU, even with no
clients connected. Admittedly my CPU is down at 800MHz, one core most of the
time.
Normally JACK stays below 2% though.
The kernel is:
3.9.0rc6 SMP PREEMPT (self built)
For some reason I couldn't use JACKD2 - and at the time it wasn't advised
anyway.
Any idea, why this CPU-hunger might creep up? Things to look into? I'd be very
grateful for hints.
Ta-ta,
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter: http://twitter.com/ffanci_silvain
* GitHub: https://github.com/fsilvain
9 Aug
9 Aug
3:47 p.m.
On Tue, Aug 9, 2016 at 2:41 PM, Ffanci Silvain <silvain(a)freeshell.de>
wrote:
for a few months now my jackd1 (0.121.3) takes on a lot of CPU, even with
no clients connected.
Are there any connections like system:capture -> system:playback?
Normally JACK stays below 2% though.
If it "builds" over time, is it linear, or is it around 2% for a long time,
and then builds to 90% or so?
It smells a bit of floating point denormal-processing, if its creeping up
after a while of not being used. I don't know if/why JACK is performing
floating ops unless there are buffers that need to be combined...
system cap1 \
system cap2 - system play1
system cap3 /
The above might explain it though - routing multiple inputs to one output.
Any idea, why this CPU-hunger might creep up? Things
to look into? I'd be
very grateful for hints.
The above is a "shot in the dark", but as far as I can see it could be a
cause.
HTH! -Harry
--
http://www.openavproductions.com
4:11 p.m.
Harry van Haaren, Aug 9 2016:
...
Are there any connections like system:capture ->
system:playback?
No.
...
If it "builds" over time, is it linear, or
is it around 2% for a long time,
and then builds to 90% or so?
I haven't watched it constantly, but it appears
to spontaneously jump or rise quickly. I'll keep a closer eye though.
My system is running 24/7, mostly handling a bit of mail, some audio playing (mpv) and
other menial tasks. CPU scheduling policy is set to constant at either 800MHz single core
- for most of the time - and 3GHz, quadcore, when recording.
It smells a bit of floating point denormal-processing,
if its creeping up
after a while of not being used. I don't know if/why JACK is performing
floating ops unless there are buffers that need to be combined...
Hm, it's a
first thought. We'll see.
Thank you for the quick response!
...
Ta-ta,
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter: http://twitter.com/ffanci_silvain
* GitHub: https://github.com/fsilvain
3056
days inactive
3056
days old
linux-audio-user@lists.linuxaudio.org
2 comments
2 participants
participants (2)
-
Ffanci Silvain -
Harry van Haaren