Re: [linux-audio-dev] TiMidity as a CPU hog

New Message Reply About this list Date view Thread view Subject view Author view Other groups

Subject: Re: [linux-audio-dev] TiMidity as a CPU hog
From: Greg Lee (greg_AT_ling.lll.hawaii.edu)
Date: Thu Jun 10 2004 - 22:40:33 EEST


Dave Phillips wrote:
> Greetings:
>
> Can someone explain why TiMidity eventually hogs the CPU at 95% or more
> after running for a while (like 12 hours or more) ? I'm talking about
> hogging the chip while TiMidity is idling, not playing.

I'd guess that it is actually playing -- busy running through all its
calculations on an empty input midi stream and playing silence. But
I don't understand why it would hog more and more over time. Maybe
it's channel filters that accumulate. Those are ordinarily
reinitialized at the beginning of each midi file, but when it's
a server, perhaps there are no new beginnings, and if a filter
is ever used on a channel, it persists to the end of server time.
Filters take lots of computation.

Greg


New Message Reply About this list Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : Thu Jun 10 2004 - 22:33:16 EEST