[mythtv] Ticket #10414: HDHomeRun: Bad Recordings (was: Bad Recordings - Choppy Playback)

Tom Lichti tom at redpepperracing.com
Sun Mar 11 14:50:23 UTC 2012

On Sat, Mar 10, 2012 at 8:41 PM, Gary Buhrmaster
<gary.buhrmaster at gmail.com> wrote:
> On Sun, Mar 11, 2012 at 00:44, Marc Randolph <mrand at pobox.com> wrote:
> ....
>> Wow.  http://fasterdata.es.net/fasterdata/host-tuning/linux/ seems to
>> suggest that values 10x smaller would be about good enough for a 10
>> Gbps network, and that going overboard actually hurts performance.
>> Wonder which site is right.
> The ESNet site recommendations are targeted for a specific
> type of application (TCP based bulk data transfers over longer
> distances, with (recommended for best results) dedicated
> high performance hosts) that are correct for that application.
> If the buffers are "too big" or "too small" you can end up
> creating some interesting issues in that targeted space.
> For a local area network (on which most people are running
> their MythTV systems) running UDP based applications,
> some of the recommendations are going to be different.
> Except for very memory limited systems, increasing the
> rmem_max values modestly will not be a negative.  Note
> that linux since an early 2.6 kernel has had TCP autotuning,
> making many of the past adjustments unnecessary
> (and sometimes harmful).

Then may I respectfully suggest that we are going down the wrong path
on this? I've used the default network settings, the tweaked settings
on the page Daniel suggested, and Daniel's own settings, and none of
them has made a difference. The only thing that made any noticeable
difference was Daniel's commit the other day, but that only made
recordings go from completely un-watchable to highly annoying (and
still un-watchable).


More information about the mythtv-dev mailing list