HDMI CEC struggles & wireless network performance on new Vero 4K+

jaybird · 1 July 2019 08:31

Hi all,

Been tinkering with my new Vero 4K+ box for the past week or so after a good 3 weeks of wait to have the parcel clearing customs and delivered to Australia.

Despite having issues getting the unit up and running initially (unit stalled on verbose loading screen, had to reload the software via SD card) along with minor issues integrating it into my setup, plenty of support topics helped me get through it.

However, there’s two major issues I couldn’t nail down:

tl;dr -
1. HDMI-CEC devices powers up randomly when Vero 4K+ box is introduced into current setup.
2. NFS data transmits at 95-130Mbps as compared to iperf3 tests achieving 200Mbps over Wi-Fi.

1. HDMI-CEC inter-operability with existing hardware

Current setup:

*Panasonic FZ950 in AU = FZ800 in UK/EU

Vero 4K+, TV and sound bar (excluding ATV4K) does not want to stay in standby, they power back up - used to be random, now they’re consistently powering back up - whenever standby command is sent from TV or sound bar.

To reproduce according to the logs uploaded…

Reboot unit, put TV to sleep using TV remote, CEC puts sound bar and Vero 4K+ into standby - Everything stays in standby after 1st reboot.
Wake unit up using Vero 4K+ remote, TV comes on, screen flashes (blank and back on) once, almost as if it received some CEC commands.
Put TV to sleep using TV remote, CEC puts sound bar and Vero 4K+ into standby - Everything powers back up about 2-3 seconds after.

What I have tried/observed:

Disabled “switch source to this device on startup” in libCEC with no change to condition.

Disabling any CEC actions when power state/source changes in libCEC with no change to condition.

Issue will only happen when Vero 4K input source is selected on sound bar.

Manually sending CEC standby commands (via SSH > cec-client) to sound bar and TV individually does not result in devices powering back on.

Swapped out different old and brand new 4K/HDR/3D/Ethernet/18Gbps+ rated HDMI cables.

Disabling libCEC on Vero4K+ randomly causes ARC on TV to disable (unable to re-enable ARC on TV at all) and ATV unable to enable and control via CEC.

Disabling CEC (Samsung Anynet+) on sound bar stops the random wake-up.

Disconnecting Vero 4K+ from the device chain everything goes back to normal.

Swapped devices between HDMI 1 and 2 inputs on sound bar with no change to condition.

Tried re-registering TV and sound bar by turning CEC feature on-off-on, along with restarting devices with no change to condition.

All devices have latest available software/firmware installed.

2. Wireless networking performance issue

The second issue I’m encountering is less annoying but would be good to get some insights.

Current setup:

Wireless AP is an Ubiquiti nanoHD, supports 4x4 stream MU-MIMO on the 5GHz radio band.
Line of sight between wireless AP and Vero 4K+, approximately 6 metres distance, minimal interference observed on channels used.
Vero 4K+ is connected to the 5GHz radio (separate SSID to the 2.4GHz radio) and can attain 390Mbps - 433Mbps receive rate as reported by Ubiquiti dashboard - The maximum of 1x1 802.11ac stream limited by the Vero 4K+ hardware to my knowledge.
XigmaNAS hosting NFS share, GbE interface, connected to GbE switch.

Situation encountered:

When streaming 4K movies, file server monitoring graph shows throughput between 95-120Mbps.
NFS mounted via autofs, achieves 95-130Mbps max using dd read test (dd if=testfile of=/dev/null)
iperf3 receive test (from server) achieves 200+Mbps

Whilst I’ve not had many issues with most 4K media after setting up autofs NFS connection and increasing my network cache on the Vero 4K+ substantially, there has been a handful titles where the total bitrate exceeds 150Mbps for duration longer than what the cache can hold, causing the playback to stall and buffer.

I understand that it is not ideal to be streaming 4K movies over wireless, due to a limitation in my residence, I’m unable to run Ethernet cables between rooms, thus I having to rely on wireless network.

It would be good to know where the limitation may be and if there’s a way to increase the streaming throughput.

Any help will be very much appreciated.

darwindesign · 1 July 2019 15:24

If you have the “AUTO-OPTIMIZE NETWORK” turned on in your controller (settings > site) you might try turning it off and see if that pushes you in the right direction. Ubiquity is still working out bugs with that system and with some devices it can hurt network performance.

dillthedog · 1 July 2019 15:43

You’ve not shown us the output (in both directions) from iperf3. Sometimes that can reveal issues.

What’s the speed if you run dd with a block size of 1MB? dd if=testfile of=/dev/null bs=1M It can sometimes make a big difference since the default dd block size is only 512 bytes.

jaybird · 1 July 2019 21:41

No luck unfortunately, performance tested on both options (on and off) does not have any notable effects to the results.

jaybird · 1 July 2019 21:54

I have since fixed the AP to a static radio channel as I’ve noticed that it’s giving me consistently higher throughput.

iperf3 tests on both directions appears to be consistently higher than what dd test can attain over NFS:

iperf “send” from Vero

osmc@osmc:/mnt/Media$ iperf3 -c 192.168.1.10
Connecting to host 192.168.1.10, port 5201
[  4] local 192.168.1.199 port 50070 connected to 192.168.1.10 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.01   sec  27.2 MBytes   226 Mbits/sec    0    462 KBytes       
[  4]   1.01-2.00   sec  26.2 MBytes   221 Mbits/sec    0    609 KBytes       
[  4]   2.00-3.00   sec  26.3 MBytes   221 Mbits/sec    0    740 KBytes       
[  4]   3.00-4.00   sec  25.9 MBytes   218 Mbits/sec    0    863 KBytes       
[  4]   4.00-5.00   sec  25.7 MBytes   216 Mbits/sec    0    899 KBytes       
[  4]   5.00-6.00   sec  26.1 MBytes   218 Mbits/sec    0    899 KBytes       
[  4]   6.00-7.01   sec  25.7 MBytes   215 Mbits/sec    0    899 KBytes       
[  4]   7.01-8.02   sec  26.1 MBytes   216 Mbits/sec    0    899 KBytes       
[  4]   8.02-9.00   sec  25.8 MBytes   220 Mbits/sec    0    899 KBytes       
[  4]   9.00-10.00  sec  25.8 MBytes   216 Mbits/sec    0    899 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec   261 MBytes   219 Mbits/sec    0             sender
[  4]   0.00-10.00  sec   259 MBytes   217 Mbits/sec                  receiver

iperf Done.

Ubiquiti Controller Stats:

Channel 56 (11ac)
Signal 69% (-63 dBm)
Rx Rate 433 Mbps
Tx Rate 433 Mbps
Power Save Not enabled

Activity 226 Mbps

iperf “receive” on Vero

osmc@osmc:/mnt/Media$ iperf3 -R -c 192.168.1.10
Connecting to host 192.168.1.10, port 5201
Reverse mode, remote host 192.168.1.10 is sending
[  4] local 192.168.1.199 port 50068 connected to 192.168.1.10 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec  34.3 MBytes   288 Mbits/sec                  
[  4]   1.00-2.00   sec  36.3 MBytes   305 Mbits/sec                  
[  4]   2.00-3.00   sec  37.0 MBytes   310 Mbits/sec                  
[  4]   3.00-4.00   sec  37.0 MBytes   310 Mbits/sec                  
[  4]   4.00-5.00   sec  36.7 MBytes   308 Mbits/sec                  
[  4]   5.00-6.00   sec  35.4 MBytes   297 Mbits/sec                  
[  4]   6.00-7.00   sec  36.8 MBytes   308 Mbits/sec                  
[  4]   7.00-8.00   sec  36.9 MBytes   310 Mbits/sec                  
[  4]   8.00-9.00   sec  37.0 MBytes   311 Mbits/sec                  
[  4]   9.00-10.00  sec  36.7 MBytes   308 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec   366 MBytes   307 Mbits/sec    0             sender
[  4]   0.00-10.00  sec   366 MBytes   307 Mbits/sec                  receiver

iperf Done.

Ubiquiti Controller Stats:

Channel 56 (11ac)
Signal 69% (-63 dBm)
Rx Rate 433 Mbps
Tx Rate 433 Mbps
Power Save Not enabled

Activity 301 Mbps

Re-ran the dd tests (test file is 4GBytes filled with zeroes):

osmc@osmc:/mnt/Media$ dd if=test.file of=/dev/null bs=1M
4096+0 records in
4096+0 records out
4294967296 bytes (4.3 GB, 4.0 GiB) copied, 202.254 s, 21.2 MB/s

osmc@osmc:/mnt/Media$ dd if=test.file of=/dev/null
8388608+0 records in
8388608+0 records out
4294967296 bytes (4.3 GB, 4.0 GiB) copied, 218.036 s, 19.7 MB/s

Ubiquiti Controller Stats:

Channel 56 (11ac)
Signal 67% (-64 dBm)
Rx Rate 433 Mbps
Tx Rate 433 Mbps
Power Save Not enabled

Activity 133 Mbps

I’ve also ran dd read test on the NAS box itself:

tardis: Media# dd if=test.file of=/dev/null
8388608+0 records in
8388608+0 records out
4294967296 bytes transferred in 29.700716 secs (144608209 bytes/sec)

tardis: Media# dd if=test.file of=/dev/null bs=1M
4096+0 records in
4096+0 records out
4294967296 bytes transferred in 7.076078 secs (606970009 bytes/sec)

Any ideas?

darwindesign · 2 July 2019 04:49

I would try a channel that is not in the DFS range. Even if that is not the issue there are good reasons to avoid them anyway.

jaybird · 2 July 2019 05:18

I was on a non-DFS channel on previous tests, being on a DFS channel actually gave better throughput in tests as compared to previous tests.

dillthedog · 2 July 2019 06:46

The iperf3 figures are pretty much in line with what I’d expect. Apparently the Vero4K is a 2(RX)x1(TX) device (I’m assuming the Vero4K+ is the same in this respect), so that would explain why the iperf3 figures are around 219 Mbps send and 307 Mbps receive. Those are better than the “200+Mbps” receive figures reported in the original post.

dd is an imperfect tool for measuring throughput but your latest figures show 21.2 MBps with a 1M block size, which is around 170 Mbps when reading the file. That’s better than the “95-130 Mbps max” reported in the original post. That said, those graphs are quite “spiky”, so perhaps something could be improved, though it might be specific to dd. Are they equally spiky when you run iperf3?

You might want to look at using iozone3 or bonnie++ for testing the throughput. (Neither is installed on OSMC.) To get you started, you can try:

bonnie++ -b -d /mnt/Media

-b bypasses the write cache. You’ll need write permission to the NFS share to run this.

jaybird · 2 July 2019 07:51

I would hazard a guess that the increase in performance due to the change from a standard to DFS channel on the 5GHz band (155 > 56) as that’s the only variable I’ve changed between the original tests and the latter.

osmc@osmc:~$ bonnie++ -b -d /mnt/Media/_test
Writing a byte at a time...done
Writing intelligently...done
Rewriting...done
Reading a byte at a time...done
Reading intelligently...done
start 'em...done...done...done...done...done...
Create files in sequential order...done.
Stat files in sequential order...done.
Delete files in sequential order...done.
Create files in random order...done.
Stat files in random order...done.
Delete files in random order...done.
Version  1.97       ------Sequential Output------ --Sequential Input- --Random-
Concurrency   1     -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
osmc          3576M   382  96 25392   6  8346   6  1053  97 18116   5 387.3  53
Latency             29425us    8399ms    7258ms   19942us     550ms     654ms
Version  1.97       ------Sequential Create------ --------Random Create--------
osmc                -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
              files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
                 16    49   2  6733  13    98   2    49   2    99   2   100   2
Latency               519ms     793ms     509ms     267ms     143ms   32805us
1.97,1.97,osmc,1,1562053497,3576M,,382,96,25392,6,8346,6,1053,97,18116,5,387.3,53,16,,,,,49,2,6733,13,98,2,49,2,99,2,100,2,29425us,8399ms,7258ms,19942us,550ms,654ms,519ms,793ms,509ms,267ms,143ms,32805us

From what I can see in the monitoring graphs on the NAS, it appears that the initial write test peaks at ~225Mbps, which looks to be in line with the iperf3 test.

The read test to fluctuate between 100-160, with odd peaks to 200Mbps.

Based on the results, this sounds to me like an issue with how NFS interacts with the underlying file system (ZFS). Thoughts?

P/s: Here’s another kicker, I’ve dragged out a long noodle of Cat6 cable to physically wire Vero 4K+ into the switch for testing…

osmc@osmc:/mnt/Media$ dd if=test.file of=/dev/null bs=1M
4096+0 records in
4096+0 records out
4294967296 bytes (4.3 GB, 4.0 GiB) copied, 36.6882 s, 117 MB/s

dillthedog · 2 July 2019 08:23

The block writes are pretty much saturating the link (25,392 KBps) but the block reads are surprisingly slow (18,116 KBps). The rewrite portion in the middle of the graph also shows consistenly better writes than reads.

IMO, the issue could be at the FreeNAS end or at the Vero4K+ end, for example an incorrectly sized NFS buffer.

Could you also provide the graphs for iperf3 in both directions?

jaybird · 2 July 2019 08:27

I’ll re-run iperf3 test over Wi-Fi shortly but interestingly here’s the bonnie++ results when ran over GigE:

osmc@osmc:/mnt/Media/_test$ bonnie++ -b -d /mnt/Media/_test
Writing a byte at a time...done
Writing intelligently...done
Rewriting...done
Reading a byte at a time...done
Reading intelligently...done
start 'em...done...done...done...done...done...
Create files in sequential order...done.
Stat files in sequential order...done.
Delete files in sequential order...done.
Create files in random order...done.
Stat files in random order...done.
Delete files in random order...done.
Version  1.97       ------Sequential Output------ --Sequential Input- --Random-
Concurrency   1     -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
osmc          3576M   387  98 72968  14 39977  20   995  99 114497  26 536.7  68
Latency             48148us    2599ms    3420ms   43349us   25408us     606ms
Version  1.97       ------Sequential Create------ --------Random Create--------
osmc                -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
              files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
                 16   549  18 29173  46  1083  17   468  16   988  14   808  14
Latency             11708us     121ms    8069us   11487us    7036us   10102us
1.97,1.97,osmc,1,1562052262,3576M,,387,98,72968,14,39977,20,995,99,114497,26,536.7,68,16,,,,,549,18,29173,46,1083,17,468,16,988,14,808,14,48148us,2599ms,3420ms,43349us,25408us,606ms,11708us,121ms,8069us,11487us,7036us,10102us

It looks like sequential reads are consistently saturating the GigE connection.

dillthedog · 2 July 2019 08:32

Indeed. Nice detective work. And this time the writes (72,968 KBps) are slower than the reads (114,497 KBps), which is more normal.

So it’s looking like it’s an issue somewhere on the WiFi side. Again, possibly a tunable parameter on the V4K+. Perhaps @sam_nazarko can provide some guidance. Unfortunately, for now I need to do some work.

And don’t forget the iperf3 graphs!

jaybird · 2 July 2019 08:48

Many thanks for your time so far to be able to bounce ideas off for testing.

So here’s the iperf3 graph…

Red is the server sending data, green is the server receiving iperf3 data from Vero over Wi-Fi.

Vero receive results:

osmc@osmc:~$ iperf3 -R -c 192.168.1.10 -t 60
Connecting to host 192.168.1.10, port 5201
Reverse mode, remote host 192.168.1.10 is sending
[  4] local 192.168.1.199 port 50129 connected to 192.168.1.10 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec  23.2 MBytes   194 Mbits/sec                  
[  4]   1.00-2.00   sec  29.0 MBytes   243 Mbits/sec                  
[  4]   2.00-3.00   sec  30.9 MBytes   259 Mbits/sec                  
[  4]   3.00-4.00   sec  32.1 MBytes   269 Mbits/sec                  
[  4]   4.00-5.00   sec  32.2 MBytes   271 Mbits/sec                  
[  4]   5.00-6.00   sec  32.4 MBytes   272 Mbits/sec                  
[  4]   6.00-7.00   sec  32.5 MBytes   273 Mbits/sec                  
[  4]   7.00-8.00   sec  27.8 MBytes   233 Mbits/sec                  
[  4]   8.00-9.00   sec  31.5 MBytes   264 Mbits/sec                  
[  4]   9.00-10.00  sec  32.3 MBytes   271 Mbits/sec                  
[  4]  10.00-11.00  sec  32.1 MBytes   270 Mbits/sec                  
[  4]  11.00-12.00  sec  32.6 MBytes   273 Mbits/sec                  
[  4]  12.00-13.00  sec  32.4 MBytes   272 Mbits/sec                  
[  4]  13.00-14.00  sec  32.8 MBytes   275 Mbits/sec                  
[  4]  14.00-15.00  sec  32.5 MBytes   272 Mbits/sec                  
[  4]  15.00-16.00  sec  32.5 MBytes   272 Mbits/sec                  
[  4]  16.00-17.00  sec  32.5 MBytes   273 Mbits/sec                  
[  4]  17.00-18.00  sec  32.6 MBytes   273 Mbits/sec                  
[  4]  18.00-19.00  sec  32.7 MBytes   274 Mbits/sec                  
[  4]  19.00-20.00  sec  32.9 MBytes   276 Mbits/sec                  
[  4]  20.00-21.00  sec  32.7 MBytes   274 Mbits/sec                  
[  4]  21.00-22.00  sec  32.8 MBytes   275 Mbits/sec                  
[  4]  22.00-23.00  sec  32.9 MBytes   276 Mbits/sec                  
[  4]  23.00-24.00  sec  32.8 MBytes   275 Mbits/sec                  
[  4]  24.00-25.00  sec  32.5 MBytes   272 Mbits/sec                  
[  4]  25.00-26.00  sec  32.6 MBytes   273 Mbits/sec                  
[  4]  26.00-27.00  sec  32.7 MBytes   274 Mbits/sec                  
[  4]  27.00-28.00  sec  32.3 MBytes   271 Mbits/sec                  
[  4]  28.00-29.00  sec  32.2 MBytes   270 Mbits/sec                  
[  4]  29.00-30.00  sec  32.3 MBytes   271 Mbits/sec                  
[  4]  30.00-31.00  sec  31.9 MBytes   268 Mbits/sec                  
[  4]  31.00-32.00  sec  32.3 MBytes   271 Mbits/sec                  
[  4]  32.00-33.00  sec  32.2 MBytes   270 Mbits/sec                  
[  4]  33.00-34.00  sec  31.8 MBytes   267 Mbits/sec                  
[  4]  34.00-35.00  sec  32.4 MBytes   272 Mbits/sec                  
[  4]  35.00-36.00  sec  32.5 MBytes   272 Mbits/sec                  
[  4]  36.00-37.00  sec  32.2 MBytes   270 Mbits/sec                  
[  4]  37.00-38.00  sec  31.6 MBytes   265 Mbits/sec                  
[  4]  38.00-39.00  sec  32.2 MBytes   270 Mbits/sec                  
[  4]  39.00-40.00  sec  31.3 MBytes   263 Mbits/sec                  
[  4]  40.00-41.00  sec  32.2 MBytes   270 Mbits/sec                  
[  4]  41.00-42.00  sec  32.3 MBytes   271 Mbits/sec                  
[  4]  42.00-43.00  sec  32.5 MBytes   273 Mbits/sec                  
[  4]  43.00-44.00  sec  31.6 MBytes   265 Mbits/sec                  
[  4]  44.00-45.00  sec  32.0 MBytes   268 Mbits/sec                  
[  4]  45.00-46.00  sec  32.0 MBytes   269 Mbits/sec                  
[  4]  46.00-47.00  sec  31.7 MBytes   266 Mbits/sec                  
[  4]  47.00-48.00  sec  30.1 MBytes   252 Mbits/sec                  
[  4]  48.00-49.00  sec  32.4 MBytes   272 Mbits/sec                  
[  4]  49.00-50.00  sec  32.0 MBytes   268 Mbits/sec                  
[  4]  50.00-51.00  sec  31.6 MBytes   265 Mbits/sec                  
[  4]  51.00-52.00  sec  31.5 MBytes   264 Mbits/sec                  
[  4]  52.00-53.00  sec  32.4 MBytes   272 Mbits/sec                  
[  4]  53.00-54.00  sec  32.4 MBytes   272 Mbits/sec                  
[  4]  54.00-55.00  sec  30.7 MBytes   257 Mbits/sec                  
[  4]  55.00-56.00  sec  25.8 MBytes   216 Mbits/sec                  
[  4]  56.00-57.00  sec  35.8 MBytes   300 Mbits/sec                  
[  4]  57.00-58.00  sec  35.8 MBytes   300 Mbits/sec                  
[  4]  58.00-59.00  sec  35.9 MBytes   301 Mbits/sec                  
[  4]  59.00-60.00  sec  35.9 MBytes   301 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-60.00  sec  1.88 GBytes   269 Mbits/sec   60             sender
[  4]   0.00-60.00  sec  1.88 GBytes   269 Mbits/sec                  receiver 

iperf Done.

Vero send results:

osmc@osmc:~$ iperf3 -c 192.168.1.10 -t 60
Connecting to host 192.168.1.10, port 5201
[  4] local 192.168.1.199 port 50131 connected to 192.168.1.10 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.00   sec  26.5 MBytes   221 Mbits/sec    0    485 KBytes       
[  4]   1.00-2.00   sec  26.2 MBytes   220 Mbits/sec    0    646 KBytes       
[  4]   2.00-3.00   sec  26.2 MBytes   219 Mbits/sec    0    724 KBytes       
[  4]   3.00-4.01   sec  26.7 MBytes   222 Mbits/sec    0    724 KBytes       
[  4]   4.01-5.00   sec  25.7 MBytes   217 Mbits/sec    0    724 KBytes       
[  4]   5.00-6.00   sec  25.8 MBytes   217 Mbits/sec    0    740 KBytes       
[  4]   6.00-7.00   sec  25.6 MBytes   215 Mbits/sec    0    740 KBytes       
[  4]   7.00-8.01   sec  26.3 MBytes   218 Mbits/sec    0    740 KBytes       
[  4]   8.01-9.00   sec  25.5 MBytes   216 Mbits/sec    0    740 KBytes       
[  4]   9.00-10.01  sec  25.9 MBytes   217 Mbits/sec    0    741 KBytes       
[  4]  10.01-11.00  sec  25.6 MBytes   216 Mbits/sec    0    741 KBytes       
[  4]  11.00-12.01  sec  25.6 MBytes   214 Mbits/sec    0    741 KBytes       
[  4]  12.01-13.01  sec  25.7 MBytes   215 Mbits/sec    0    741 KBytes       
[  4]  13.01-14.01  sec  25.9 MBytes   216 Mbits/sec    0    741 KBytes       
[  4]  14.01-15.02  sec  25.6 MBytes   213 Mbits/sec    0    741 KBytes       
[  4]  15.02-16.00  sec  25.6 MBytes   218 Mbits/sec    0    755 KBytes       
[  4]  16.00-17.01  sec  25.5 MBytes   213 Mbits/sec    0    755 KBytes       
[  4]  17.01-18.01  sec  25.7 MBytes   216 Mbits/sec    0    755 KBytes       
[  4]  18.01-19.00  sec  25.8 MBytes   217 Mbits/sec    0    755 KBytes       
[  4]  19.00-20.00  sec  26.4 MBytes   221 Mbits/sec    0    755 KBytes       
[  4]  20.00-21.00  sec  25.8 MBytes   216 Mbits/sec    0    755 KBytes       
[  4]  21.00-22.00  sec  26.0 MBytes   219 Mbits/sec    0    772 KBytes       
[  4]  22.00-23.00  sec  26.4 MBytes   221 Mbits/sec    0    772 KBytes       
[  4]  23.00-24.01  sec  26.5 MBytes   220 Mbits/sec    0    772 KBytes       
[  4]  24.01-25.00  sec  25.6 MBytes   217 Mbits/sec    0    772 KBytes       
[  4]  25.00-26.00  sec  25.6 MBytes   215 Mbits/sec    0    773 KBytes       
[  4]  26.00-27.01  sec  25.7 MBytes   215 Mbits/sec    0    773 KBytes       
[  4]  27.01-28.00  sec  25.8 MBytes   217 Mbits/sec    0    773 KBytes       
[  4]  28.00-29.01  sec  26.3 MBytes   219 Mbits/sec    0    773 KBytes       
[  4]  29.01-30.01  sec  26.1 MBytes   218 Mbits/sec    0    773 KBytes       
[  4]  30.01-31.00  sec  25.9 MBytes   219 Mbits/sec    0    773 KBytes       
[  4]  31.00-32.01  sec  25.6 MBytes   214 Mbits/sec    0    773 KBytes       
[  4]  32.01-33.00  sec  25.6 MBytes   215 Mbits/sec    0    773 KBytes       
[  4]  33.00-34.00  sec  25.7 MBytes   216 Mbits/sec    0    773 KBytes       
[  4]  34.00-35.01  sec  26.2 MBytes   218 Mbits/sec    0    773 KBytes       
[  4]  35.01-36.00  sec  25.5 MBytes   215 Mbits/sec    0    773 KBytes       
[  4]  36.00-37.01  sec  25.8 MBytes   215 Mbits/sec    0    773 KBytes       
[  4]  37.01-38.00  sec  25.6 MBytes   215 Mbits/sec    0    773 KBytes       
[  4]  38.00-39.01  sec  25.8 MBytes   216 Mbits/sec    0    773 KBytes       
[  4]  39.01-40.00  sec  23.9 MBytes   201 Mbits/sec    0    773 KBytes       
[  4]  40.00-41.01  sec  26.0 MBytes   216 Mbits/sec    0    773 KBytes       
[  4]  41.01-42.00  sec  26.1 MBytes   221 Mbits/sec    0    788 KBytes       
[  4]  42.00-43.01  sec  25.7 MBytes   215 Mbits/sec    0    788 KBytes       
[  4]  43.01-44.01  sec  26.0 MBytes   217 Mbits/sec    0    789 KBytes       
[  4]  44.01-45.00  sec  25.8 MBytes   217 Mbits/sec    0    789 KBytes       
[  4]  45.00-46.00  sec  25.8 MBytes   217 Mbits/sec    0    789 KBytes       
[  4]  46.00-47.01  sec  26.1 MBytes   218 Mbits/sec    0    789 KBytes       
[  4]  47.01-48.00  sec  25.6 MBytes   216 Mbits/sec    0    789 KBytes       
[  4]  48.00-49.00  sec  25.7 MBytes   215 Mbits/sec    0    789 KBytes       
[  4]  49.00-50.00  sec  25.6 MBytes   214 Mbits/sec    0    789 KBytes       
[  4]  50.00-51.00  sec  25.4 MBytes   213 Mbits/sec    0    789 KBytes       
[  4]  51.00-52.00  sec  26.6 MBytes   223 Mbits/sec    0    789 KBytes       
[  4]  52.00-53.00  sec  25.8 MBytes   217 Mbits/sec    0    789 KBytes       
[  4]  53.00-54.00  sec  26.0 MBytes   218 Mbits/sec    0    789 KBytes       
[  4]  54.00-55.00  sec  25.8 MBytes   216 Mbits/sec    0    789 KBytes       
[  4]  55.00-56.01  sec  25.8 MBytes   216 Mbits/sec    0    789 KBytes       
[  4]  56.01-57.00  sec  26.1 MBytes   220 Mbits/sec    0    789 KBytes       
[  4]  57.00-58.00  sec  25.8 MBytes   216 Mbits/sec    0    789 KBytes       
[  4]  58.00-59.00  sec  26.1 MBytes   219 Mbits/sec    0    789 KBytes       
[  4]  59.00-60.01  sec  25.3 MBytes   212 Mbits/sec    0    789 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-60.01  sec  1.51 GBytes   217 Mbits/sec    0             sender
[  4]   0.00-60.01  sec  1.51 GBytes   216 Mbits/sec                  receiver

iperf Done.

I don’t think it’s related but I’ve noted an interesting behaviour whilst having Vero on the wireless section of My OSMC app…

I’m presuming it’s either CPU or wireless hardware scanning for available APs?

osmc@osmc:~$ iperf3 -R -c 192.168.1.10 -t 60
Connecting to host 192.168.1.10, port 5201
Reverse mode, remote host 192.168.1.10 is sending
[  4] local 192.168.1.199 port 50124 connected to 192.168.1.10 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec  17.6 MBytes   148 Mbits/sec                  
[  4]   1.00-2.00   sec  28.5 MBytes   239 Mbits/sec                  
[  4]   2.00-3.00   sec  30.7 MBytes   257 Mbits/sec                  
[  4]   3.00-4.00   sec  31.5 MBytes   264 Mbits/sec                  
[  4]   4.00-5.00   sec  19.6 MBytes   164 Mbits/sec                  
[  4]   5.00-6.00   sec  6.56 MBytes  55.0 Mbits/sec                  
[  4]   6.00-7.00   sec  3.82 MBytes  32.1 Mbits/sec                  
[  4]   7.00-8.00   sec  4.63 MBytes  38.8 Mbits/sec                  
[  4]   8.00-9.00   sec  18.4 MBytes   155 Mbits/sec                  
[  4]   9.00-10.00  sec  27.2 MBytes   228 Mbits/sec                  
[  4]  10.00-11.00  sec  29.5 MBytes   248 Mbits/sec                  
[  4]  11.00-12.00  sec  31.2 MBytes   262 Mbits/sec                  
[  4]  12.00-13.00  sec  17.5 MBytes   147 Mbits/sec                  
[  4]  13.00-14.00  sec  6.83 MBytes  57.3 Mbits/sec                  
[  4]  14.00-15.00  sec  4.63 MBytes  38.9 Mbits/sec                  
[  4]  15.00-16.00  sec  4.59 MBytes  38.5 Mbits/sec                  
[  4]  16.00-17.00  sec  21.6 MBytes   181 Mbits/sec                  
[  4]  17.00-18.00  sec  28.6 MBytes   240 Mbits/sec                  
[  4]  18.00-19.00  sec  30.5 MBytes   256 Mbits/sec                  
[  4]  19.00-20.00  sec  31.9 MBytes   268 Mbits/sec                  
[  4]  20.00-21.00  sec  19.9 MBytes   167 Mbits/sec                  
[  4]  21.00-22.00  sec  6.68 MBytes  56.0 Mbits/sec                  
[  4]  22.00-23.00  sec  4.60 MBytes  38.6 Mbits/sec                  
[  4]  23.00-24.00  sec  3.87 MBytes  32.5 Mbits/sec                  
[  4]  24.00-25.00  sec  21.1 MBytes   177 Mbits/sec                  
[  4]  25.00-26.00  sec  28.8 MBytes   242 Mbits/sec                  
[  4]  26.00-27.00  sec  30.8 MBytes   258 Mbits/sec                  
[  4]  27.00-28.00  sec  27.6 MBytes   232 Mbits/sec                  
[  4]  28.00-29.00  sec  16.8 MBytes   141 Mbits/sec                  
[  4]  29.00-30.00  sec  6.07 MBytes  51.0 Mbits/sec                  
[  4]  30.00-31.00  sec  3.97 MBytes  33.3 Mbits/sec                  
[  4]  31.00-32.00  sec  4.84 MBytes  40.6 Mbits/sec                  
[  4]  32.00-33.00  sec  19.6 MBytes   165 Mbits/sec                  
[  4]  33.00-34.00  sec  28.7 MBytes   241 Mbits/sec                  
[  4]  34.00-35.00  sec  30.5 MBytes   256 Mbits/sec                  
[  4]  35.00-36.00  sec  31.4 MBytes   263 Mbits/sec                  
[  4]  36.00-37.00  sec  25.5 MBytes   214 Mbits/sec                  
[  4]  37.00-38.00  sec  4.98 MBytes  41.8 Mbits/sec                  
[  4]  38.00-39.00  sec  5.12 MBytes  42.9 Mbits/sec                  
[  4]  39.00-40.00  sec  5.12 MBytes  43.0 Mbits/sec                  
[  4]  40.00-41.00  sec  12.1 MBytes   102 Mbits/sec                  
[  4]  41.00-42.00  sec  26.1 MBytes   219 Mbits/sec                  
[  4]  42.00-43.00  sec  27.8 MBytes   234 Mbits/sec                  
[  4]  43.00-44.00  sec  30.8 MBytes   258 Mbits/sec                  
[  4]  44.00-45.00  sec  27.2 MBytes   228 Mbits/sec                  
[  4]  45.00-46.00  sec  6.42 MBytes  53.8 Mbits/sec                  
[  4]  46.00-47.00  sec  4.90 MBytes  41.1 Mbits/sec                  
[  4]  47.00-48.00  sec  4.26 MBytes  35.7 Mbits/sec                  
[  4]  48.00-49.00  sec  11.4 MBytes  95.3 Mbits/sec                  
[  4]  49.00-50.00  sec  25.8 MBytes   217 Mbits/sec                  
[  4]  50.00-51.00  sec  29.4 MBytes   247 Mbits/sec                  
[  4]  51.00-52.00  sec  31.5 MBytes   264 Mbits/sec                  
[  4]  52.00-53.00  sec  25.2 MBytes   212 Mbits/sec                  
[  4]  53.00-54.00  sec  5.99 MBytes  50.3 Mbits/sec                  
[  4]  54.00-55.00  sec  4.29 MBytes  36.0 Mbits/sec                  
[  4]  55.00-56.00  sec  4.41 MBytes  37.0 Mbits/sec                  
[  4]  56.00-57.00  sec  15.1 MBytes   127 Mbits/sec                  
[  4]  57.00-58.00  sec  28.2 MBytes   237 Mbits/sec                  
[  4]  58.00-59.00  sec  30.4 MBytes   255 Mbits/sec                  
[  4]  59.00-60.00  sec  31.3 MBytes   263 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-60.00  sec  1.08 GBytes   154 Mbits/sec  1315             sender
[  4]   0.00-60.00  sec  1.08 GBytes   154 Mbits/sec                  receiver

iperf Done.

sam_nazarko · 2 July 2019 12:24

Can you show me the autofs mount parameters?

My OSMC will be background scanning when open, so this would impact performance.

jaybird · 2 July 2019 13:00

Hi Sam,

Here are the config files:

/etc/auto.master
/- /etc/auto.nfs.shares --timeout 15 browse

/etc/auto.nfs.shares
/mnt/Media 192.168.1.10:/mnt/tank/Media

Here are the mount output:

osmc@osmc:/mnt/Media$ mount

devtmpfs on /dev type devtmpfs (rw,relatime,size=791072k,nr_inodes=197768,mode=755)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,relatime)

tmpfs on /run type tmpfs (rw,relatime)

/dev/mapper/vero--nand-root on / type ext4 (rw,relatime,stripe=1024,data=ordered)

securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)

tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)

devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)

tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)

tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)

cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)

pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)

cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)

cgroup on /sys/fs/cgroup/bfqio type cgroup (rw,nosuid,nodev,noexec,relatime,bfqio)

cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)

cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)

cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)

cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)

cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)

cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)

debugfs on /sys/kernel/debug type debugfs (rw,relatime)

mqueue on /dev/mqueue type mqueue (rw,relatime)

systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=35,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)

sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)

configfs on /sys/kernel/config type configfs (rw,relatime)

/etc/auto.nfs.shares on /mnt/Media type autofs (rw,relatime,fd=6,pgrp=500,timeout=15,minproto=5,maxproto=5,direct)

tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=183124k,mode=700,uid=1000,gid=1000)

192.168.1.10:/mnt/tank/Media on /mnt/Media type nfs (rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.10,mountvers=3,mountport=740,mountproto=udp,local_lock=none,addr=192.168.1.10)

sam_nazarko · 2 July 2019 13:45

Try adjusting the rsize value

Sam

jaybird · 2 July 2019 14:36

It looks like rsize of 131072 is the maximum allowable value, lower values resulted in lower throughput.

I might try and set up an UFS datastore on the NAS and test it over WiFI and NFS and see how it performs.

In the mean time, any suggestions with the CEC dilemma?

encdpnew · 2 July 2019 16:36

Hi jaybird, I have always found extremely similar CEC issues to the ones you describe. In my setup I have a Sony TV and Denon AVR, which have exceptionally reliable CEC with all other devices.

I also find that sometimes CEC functionality across the whole setup is broken (including ARC) until the Vero is unplugged.

I also find that if powered off by CEC, the Vero 4K invariably powers itself back on before waking everything else.

Additionally, I have observed that (invariably) if the Vero 4K is left connected by HDMI but the power cable unplugged, then CEC across the rest of the system stops working. This is really weird; that the Vero 4K can have a negative impact even when it has no power. I guess there is some small current from the HDMI connection(?)

I’ve posted about this a year or so ago but never really got anywhere I’m afraid - has been like this since day 1 and I’ve just got used to it.

If it would help to post logs from my Vero, for comparison with jaybird’s, I’d be happy to.

darwindesign · 2 July 2019 17:07

Although not where your main issue is coming from I would still suggest moving channels. From what I understand your AP must insert pauses in its transmission on DFS channels so it can check to make sure it is operating on a clear airwave. Since there is quite a few non-DFS channels and they don’t travel very far I would think you should be able to find a clear spot elsewhere. The RF scan buried in your AP settings is very useful for this purpose as it will find not only hidden networks but other sources of interference.

dillthedog · 3 July 2019 06:17

While the problem could be at the Vero4K+ end, it could equally be at the access point (ensure that the firmware is up to date), something in your network infrastructure or possibly even at the server end.

The best strategy now is to double-check all the settings of the AP and, if you have no success there, try hardware substitution: try a different port / cable / whatever. Your idea of a UFS datastore on the NAS is a good test.