Jump to content

Performance on QNAP : Docker VS qpkg (Transcoding ok)


GTsitouridis

Recommended Posts

GTsitouridis

I have an issue with docker on QNAP in terms of performance.

While I have setup transcoding and it is working just fine, I have a reduced bitrate and as a result bad image.

The source is the same (TVHeadEnd on Pi Zero).  When using qpkg I get a bitrate of 20Mbps+ while when in docker I get only 10Mbps. At least this is the only thing I can see as a difference. I am also previewing the same channel while switching from docker to qpkg.

I did not know if it had to do with networking internal of QNAP, so I tried all possible docker connection methods, all of which yielded the same results.

 

Any ideas?

Link to post
Share on other sites
Luke

Hi there, can we please look at example sessions from each so that we can compare?

Thanks !

Link to post
Share on other sites
Luke

Can you please provide the logging information requested in my link above? Thanks !

Link to post
Share on other sites
Luke

You're getting basically the same transcoding performance from both. I wonder if it's due to the disk or network performance of the docker container.

Link to post
Share on other sites
GTsitouridis
1 hour ago, Luke said:

You're getting basically the same transcoding performance from both. I wonder if it's due to the disk or network performance of the docker container.

Well.... both are running on the same physical system and on the same mirrored disks.

Link to post
Share on other sites
Luke

Right but Docker adds a virtualization layer in between. That doesn't necessarily mean it will make a substantial difference, but there is a cost to that.

Link to post
Share on other sites
GTsitouridis
2 minutes ago, Luke said:

Right but Docker adds a virtualization layer in between. That doesn't necessarily mean it will make a substantial difference, but there is a cost to that.

This is more than true. I am just reminding that we are talking about the same physical system and the same array/volume.

One other thing, is that I have allocated all available resources to the container, which is barely using them.

Edited by GTsitouridis
Link to post
Share on other sites
  • 4 weeks later...
GTsitouridis
On 1/28/2021 at 9:16 AM, Luke said:

Right but Docker adds a virtualization layer in between. That doesn't necessarily mean it will make a substantial difference, but there is a cost to that.

Hallo,

Eventually I think I figure out as to why it is happening. Comparing HW detection logs I found that native emby package on QNAP uses i965 driver, while in docker (running on QNAP) it is using iHD driver. I think this is the case with the following thread:

Hardware Encoding Issues (j4125) - Asustor - Emby Community

I simply do not know how to go about and correct it.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...