[mythtv-users] Preventing a file transfer from saturating the network

[jedi]

On Wed, Dec 24, 2014 at 10:19:48AM -0600, Mark Boyum wrote:
> You aren't copying files to the same drive that hosts your MythConverg DB
> are you?  If so, it could be that drive doesn't seek so well and is choking
> trying to handle all of the seek table updates in addition to the file copy.

    It could just be what was described. I have seen this kind of problem with
streaming services. I can start a file transfer and suck the life out of the
network such that my users complain that Netflix or Amazon is failling apart
under the strain.

    I've not really noticed problems with my HDHR but I've never really bothered
to look. The impact on streaming services is visible and immediate, so it's hard
to miss. Plus an ATSC stream can suffer from poor signal issues. I usually just
assume that's my problem with recordings.

    Something like net.nice is probably long overdue.

    Some apps (like Steam) already have this concept built in.

> 
> On Wed, Dec 24, 2014 at 12:49 AM, Neil Salstrom <salstrom at gmail.com> wrote:
> 
> > Wow.... Thanks for all the suggestions.  I guess I did leave out that
> > this was using a NFS share and simply copying the file from one to the
> > other (not using cp in a terminal).  I don't believe it's an issue
> > with hard drive read / write speed as I can watch a recorded (on disk)
> > program if a file transfer is occurring without problems.  It's only
> > if the HDHomerun is in use during the transfer.
> >
> > If theoretical speed on a gigablit lan is 125 MB/s what is real world?
> >  According to the reported transfer rate across my network I'm hitting
> > up to ~110 MB/s then I add ~2 MB/s for the ATSC stream am I bumping up
> > against real world performance of my network?
> >
> > Perhaps the easiest solution would be to pay attention to when I need
> > to transfer files!