Emby DVR running on Syno NAS, burst of packet loss

[rouq 23]

I'm running Emby server 3.3.1.0 on Synology DS418play with 6GB of RAM (emby server running on mono)  The NAS is pretty much stock, I only installed emby server on it.  I bought a HDHomerun Quatro few weeks ago.  I'm experiencing burst of big glitches in the recordings.  At first, I thought the Quatro was defective, so I contacted Silicondust support.  They requested that I activate the debug feature in the Quatro.  They told me that they see burst of packet loss.  It can be fine for several minutes, then a burst of packet loss on a short period and fine again for several minutes.  It's worst when recording 4 streams at the same time, but can see sometime burst of packet loss with only 1 stream.  On the NAS, I don't see any spike on the CPU (pretty constant at 55% with 4 streams).  The volume usage doesn't exceed 12%.

 

The NAS and the HDhomerun are connected to an unmanaged gigabit switch.  I changed the ethernet cable and I tried a different switch.  No change.  I extended the network receive buffers on the NAS (net.core.rmem_max and net.ipv4.tcp_rmem) with no change.  I change emby server process priority using renice command to -20.  This seems to help, but still see some burst of packet loss.

 

To make sure that the NAS is capable of handling this, I opened 4 ssh sessions with the NAS and started grabbing 4 streams on the quatro at the same time using curl command.  I repeat this 3 times.  There was no packet loss.  So pretty much remove the network out of the equation and the NAS is capable of grabbing 4 streams at the same time.

 

It looks like the packet loss is due to emby server running on the NAS.  I don't know what else to do to fix the packet loss issue.  Any help and advice would be greatly appreciated.

 

Also, do you think emby running on netcore instead of mono would help?  To my knowledge, the netcore version was not yet release for Synology NAS, right?

 

Attached, emby server logs.  4 recordings at 7am.  All suffers from packet loss.

 

Thank you

Log.txt

[Luke 39306]

Hi, one thing you could do is try turning off the dlna server. there is a Microsoft dlna app on your network that is hammering the server with frequent requests:

2018-04-23 08:08:54.928 Info HttpServer: HTTP Response 200 to 192.168.2.32. Time: 1ms. http://192.168.2.15:8096/dlna/25eaeea5f4034e3194d29b9376cb2a3a/description.xml 
2018-04-23 08:09:04.965 Info HttpServer: HTTP GET http://192.168.2.15:8096/dlna/25eaeea5f4034e3194d29b9376cb2a3a/description.xml. UserAgent: Microsoft-Windows/10.0 UPnP/1.0

[rouq 23]

 

Hi, one thing you could do is try turning off the dlna server. there is a Microsoft dlna app on your network that is hammering the server with frequent requests:

2018-04-23 08:08:54.928 Info HttpServer: HTTP Response 200 to 192.168.2.32. Time: 1ms. http://192.168.2.15:8096/dlna/25eaeea5f4034e3194d29b9376cb2a3a/description.xml 
2018-04-23 08:09:04.965 Info HttpServer: HTTP GET http://192.168.2.15:8096/dlna/25eaeea5f4034e3194d29b9376cb2a3a/description.xml. UserAgent: Microsoft-Windows/10.0 UPnP/1.0

 

Thank you for the suggestion.  Unfortunately, I did not resolve my issue.