[mythtv-users] BE 2 - Remote Frontends Sluggish on FF

[Barry Martin]

Hi Folks!

First, Steve: thanks for the backup information.

Second, I went back to the /iperf/  testing -- something didn't seem 
quite right but I didn't even know this test existed until a few days 
ago, so guess not doing to bad.  Ran the test 'backwards' -- switched 
client and server -- which I hadn't done the first time.  Found there 
appears to be a discrepancy, though have no idea what the next step is.



Ran iperf -c 192.168.0.21 -d   on "BE2", the Backend with which I have 
been issues with long pausing and sluggish FF, playback appears fine.

This is the results from "M58", which is not used as a Frontend:

    barry at Lenovo-M58:~$ iperf -s
    ------------------------------------------------------------
    Server listening on TCP port 5001
    TCP window size: 85.3 KByte (default)
    ------------------------------------------------------------
    [  4] local 192.168.0.21 port 5001 connected with 192.168.0.4 port 57116
    ------------------------------------------------------------
    Client connecting to 192.168.0.4, TCP port 5001
    TCP window size:  162 KByte (default)
    ------------------------------------------------------------
    [  6] local 192.168.0.21 port 33356 connected with 192.168.0.4 port 5001
    [ ID] Interval       Transfer     Bandwidth
    [  6]  0.0-10.1 sec   108 MBytes  89.6 Mbits/sec
    [  4]  0.0-10.6 sec  35.4 MBytes  28.1 Mbits/sec
    [  5] local 192.168.0.21 port 5001 connected with 192.168.0.13 port
    50268
    ------------------------------------------------------------

One direction the data travels about 3x faster than the other -- is this 
resulting in the sluggishness on the FF request?



Ran the same test on "BE1", the old Backend which has the proper and 
snappy Fast Forwarding; results; results as viewed on "M58" (same server 
as above test) :

    Client connecting to 192.168.0.13, TCP port 5001
    TCP window size:  153 KByte (default)
    ------------------------------------------------------------
    [  6] local 192.168.0.21 port 51130 connected with 192.168.0.13 port
    5001
    [  6]  0.0-10.0 sec   112 MBytes  93.4 Mbits/sec
    [  5]  0.0-10.0 sec   106 MBytes  88.5 Mbits/sec
    [  4] local 192.168.0.21 port 5001 connected with 192.168.0.13 port
    50270
    ------------------------------------------------------------
    Client connecting to 192.168.0.13, TCP port 5001
    TCP window size:  153 KByte (default)
    ------------------------------------------------------------
    [  6] local 192.168.0.21 port 51132 connected with 192.168.0.13 port
    5001
    [  4]  0.0-10.0 sec   106 MBytes  89.0 Mbits/sec
    [  6]  0.0-10.0 sec   112 MBytes  93.5 Mbits/sec
    [  5] local 192.168.0.21 port 5001 connected with 192.168.0.4 port 57204
    ------------------------------------------------------------

So on the old/original Backend (BE1) the test results are almost the 
same in both directions.


Ran the test on BE2 again:

    Client connecting to 192.168.0.4, TCP port 5001
    TCP window size:  170 KByte (default)
    ------------------------------------------------------------
    [  6] local 192.168.0.21 port 33702 connected with 192.168.0.4 port 5001
    [  6]  0.0-10.1 sec   110 MBytes  90.7 Mbits/sec
    [  5]  0.0-10.6 sec  39.4 MBytes  31.1 Mbits/sec

A hare faster for some reason but still significantly lopsided.

(Might also explain why viewing on the BE [BE2] I'm not seeing the FF 
issue ==> 'internal connection'.)

So thanks in  advance!  Probably made the presentation  more complicated 
than necessary but I have next to no idea what I'm doing.

Barry


P.S.:

     192.168.0.4    = BE2 (Backend 2), the 'side' with the sluggish Fast 
Forwarding.
     192.168.0.13    = BE1 (Backend 1), the 'side' that's old and works 
fine but will need to be replaced because of age.
     The two Backends are independent.  Frontends connected to BE1 work 
fine, same FE to BE2 exhibit the FF sluggishness.
     192.168.0.21    = M58.  Is _not_ a FE; is my desk computer.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20171108/adf37b71/attachment.html>