[mythtv-users] RingBuf(...): Waited 0.2 seconds for data to become available...
Brian J. Murrell
brian at interlinx.bc.ca
Sat Feb 18 18:16:41 UTC 2012
On 12-02-16 06:49 AM, Brian J. Murrell wrote:
> I think what is obvious above is that all disk reading was satisfied by
> the cache and the CPU was not under stress so there's really no
> resourceful reason that there should be excessive delays. I wonder if
> there is something else lurking in the code that is introducing delay.
> Or maybe such delays are normal and expected, but then I'd think it's
> not worth constantly printing messages about them.
As an additional data point, I enabled NFS between the mythjobqueue
running machine and the BE and these "Waited ... seconds" messages are gone.
Quite clearly, NFS is able to keep up with the jobs on the remote
machine. Why is Myth BE unable to keep up? I would actually think/hope
that a purpose-designed streaming protocol would be more efficient than
a general filesharing protocol like NFS, not less.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 262 bytes
Desc: OpenPGP digital signature
Url : http://www.mythtv.org/pipermail/mythtv-users/attachments/20120218/0a3929b2/attachment.bin
More information about the mythtv-users