4k buffering/stuttering

bmillham · 3 January 2018 23:41

First thing, get rid of the banned addons in your sources.xml before we continue much further

I’d suggest that you start with a clean sources.xml. (you can copy your current one to back it up) with only the fstab mounted shares.

As for the cache settings, these are the current recommended for the 4K;

 <cache>
  <memorysize>524880000</memorysize>
  <buffermode>1</buffermode>
 </cache>

Beastie · 4 January 2018 17:12

Hey

I cleaned out the config files: http://paste.osmc.tv/sonucugasu

No difference in speeds. What is weird for me, is that if i read using smbclient, the speed is way faster.

using mount in fstab:

osmc@vero:~/Movies$ dd if=/mnt/movies-d/test.file of=/dev/null bs=1M count=3072
115+1 records in
115+1 records out
121505600 bytes (122 MB) copied, 110.04 s, 1.1 MB/s

Using smbclient:

osmc@vero:~/Movies$ smbclient //192.168.1.40/movies-d --user=vero -m SMB3
Enter vero's password:
Domain=[BEASTIE] OS=[] Server=[]
smb: \> get test.file /dev/null
getting file \test.file of size 121505600 as /dev/null (12205.1 KiloBytes/sec) (average 11666.6 KiloBytes/sec)

I am confused

dillthedog · 4 January 2018 17:46

Yes, strange. What’s the output from running the command mount?

Beastie · 4 January 2018 18:35

osmc@vero:~$ mount
devtmpfs on /dev type devtmpfs (rw,relatime,size=803956k,nr_inodes=200989,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)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
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)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/bfqio type cgroup (rw,nosuid,nodev,noexec,relatime,bfqio)
systemd-1 on /mnt/movies-d type autofs (rw,relatime,fd=22,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=24,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
//192.168.1.40/movies-d on /mnt/movies-d type cifs (rw,relatime,vers=3.0,sec=ntlmssp,cache=strict,username=vero,domain=BEASTIE,uid=1000,forceuid,gid=1000,forcegid,addr=192.168.1.40,file_mode=0770,dir_mode=0770,nounix,serverino,rsize=65536,wsize=65536,actimeo=1)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=183220k,mode=700,uid=1000,gid=1000)

dillthedog · 4 January 2018 21:25

I don’t see anything obvious but the mount is using a few options that I’m unfamiliar with - nounix,serverino - and I’m unsure of their consequences. The blocksize is 65536, which should be large enough.

Out of interest, what’s the server? I noticed you had an NFS share defined in the Kodi sources.xml file for the server’s IP address. Is NFS a possibility?

Beastie · 5 January 2018 20:32

I got the options from this post: https://discourse.osmc.tv/t/configuring-fstab-based-samba-share-mounts/38167

The “server” is a Windows 10 1709 machine. I Tried to install a NFS server on the Win10, but it turns out, it’s not super easy to do that, so I never succeeded with that

dillthedog · 5 January 2018 20:50

Understood. I don’t use Win10.

Perhaps @Tom_Doyle or @fzinken might be able to take this one forward.

Tom_Doyle · 5 January 2018 20:52

Hi,

If you are using Windows I would stick to samba/cifs as the windows NFS support is iffy at best. I would suggest mounting cifs using fstab, for better throughput.

Thanks Tom.

Beastie · 5 January 2018 21:01

Hey Tom

That is what I do

Tom_Doyle · 5 January 2018 21:20

Hi,

Sorry been a long week and only speed read the thread, and seen kodi smb mounts.

As Dilthedog has advised a constant 180 Mbits/sec, should be more than amble for stable playback of 4k. Have you tried playing these files back locally from usb or sdcard?

Thanks Tom.

Beastie · 5 January 2018 21:39

Yea, I tried to connect a USB HDD directly, and then it plays fine

Tom_Doyle · 5 January 2018 22:38

Hi,

Is the the win10 machine connected to network via wired or wifi and when you ran iperf, was the win 10 machine the iperf server?

Despite my previous statement about windows nfs support being iffy (which it is) it may provide better throughput in this case, can you provide a link to the instructions you have been following?

Thanks Tom.

Beastie · 6 January 2018 01:28

Yea, the Win10 is on wired, and it was the iperf server.

I didn’t find any instructions… . So if you have any guide, I could try it

It puzzles me though, that when i use smbclient I get ok transferspeeds

fzinken · 6 January 2018 03:28

Ok so let’s not complicate things. Lets not go for NFS. Surely the smbclient differences are strange as they should use the same kernel modules. I suggest:

Check for any smb.conf files and post their content

find /home/osmc -type f -name "smb.conf" -exec paste-log "{}" \;
sudo find /etc -type f -name "smb.conf" -exec paste-log "{}" \;

Start with a fresh install as my feeling is in the meantime many things are overlapping. After fresh install start with fstab mounts directly.

bmillham · 6 January 2018 03:34

+1 for this idea. I’m also thinking that so many things have been tried that it’s just easier to start over.

Beastie · 6 January 2018 15:53

Thanks. It came up with 3 hits. I don’t think I have edited any of these files. The content is:
https://paste.osmc.tv/ipevurudig
https://paste.osmc.tv/tikovuqobu
https://paste.osmc.tv/asirahutuw

I will do a clean install, and post results.

fzinken · 6 January 2018 16:03

ok, keep us posted. I wonder did you install the Samba Server on purpose?

Beastie · 6 January 2018 16:10

Yes I did. For ease of access from my Windows machine. Not really needed though.

I can skip installing it on the fresh install.

fzinken · 6 January 2018 16:14

Well it shouldn’t harm (I have it installed on mine) but for new install I suggest you try the fstab mounts performance as the first step before installing additional stuff

Beastie · 6 January 2018 17:07

I did a fresh install, edited fstab to mount, but unfortunately it is the same performance

osmc@vero:~$ dd if=/mnt/movies-d/test.file of=/dev/null bs=1M count=3072
115+1 records in
115+1 records out
121505600 bytes (122 MB) copied, 102.228 s, 1.2 MB/s

I then installed iperf, and ran an iperf test, that is still good, avg 166Mbit/sec: https://paste.osmc.tv/fupesesepa

Any ideas?