Mailing List Archive

I've seen this too... and it bugs me. My system is fast enough to
record and playback another recording. However, when watching LiveTV I
often get very jerky motion and top shows very little idle CPU time.
However, recording and playing back another show uses 35% backend, 5-10%
frontend. Sometimes I see it behave like this, other times LiveTV
works just fine. I'm pretty aware of other background processes, and
I'm sure nothing else is causing this.

Question: Does a single backend/frontend combo system always read the
data over the TCP socket? Or does the frontend get the files straight
from the filesystem when possible?



On Wed, 2003-04-30 at 09:06, rosenbla@uchastings.edu wrote:
> The CPU usage by mythbackend seems odd to me:
> When recording only, backend uses about 45%
> When Watching a pre-recorded backend uses 0%, frontend about 5%
> When watching live TV backend uses ~70% frontend about 4%
>
> So what seems odd to me is why the backend is using 25% more on livetv then
> when it just records, if playing a recording seems to really only need frontend using
> cpu?
>
> I have checked the default and livetv profiles and they are identical both on the
> setup screen and in the mysql database. Does anyone else notice this?
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@snowman.net
> http://lists.snowman.net/cgi-bin/mailman/listinfo/mythtv-users

On Friday 02 May 2003 12:48 pm, Aran Cox wrote:
> I've seen this too... and it bugs me. My system is fast enough to
> record and playback another recording. However, when watching LiveTV I
> often get very jerky motion and top shows very little idle CPU time.
> However, recording and playing back another show uses 35% backend, 5-10%
> frontend. Sometimes I see it behave like this, other times LiveTV
> works just fine. I'm pretty aware of other background processes, and
> I'm sure nothing else is causing this.
>
> Question: Does a single backend/frontend combo system always read the
> data over the TCP socket? Or does the frontend get the files straight
> from the filesystem when possible?

Live-tv currently always goes through a TCP socket. I've never bothered
optimizing that, yet, though I plan to sometime. Playback of files will get
the data from the filesystem when possible, though.

Isaac