Emby is very slow. Reinstalled, same thing.

[bobwinters 1]

Edited: Deleted post

Log.txt

Edited January 14, 2018 by bobwinters

[ebr 16195]

Hi.  When you say "Emby takes ... to load" what, exactly, are you talking about?  The server, the web app home page, another app, etc?

 

Also, do you allow either the server containing your media or the drives to sleep?  Delays like that are many times due to waiting on hardware.

[bobwinters 1]

Edited: Deleted post

Edited January 14, 2018 by bobwinters

[ebr 16195]

Sounds a whole lot like waiting on hardware.

 

If you can reproduce this issue and post a new server log or you can tell us exactly when you performed the steps you described in the log above, we can take a look.  Thanks.

[bobwinters 1]

Just a quick update. It was hardware. I moved to Linux, same thing. I upgraded my system drive to a SSD and Emby is very functional now. I'd recommend to others to use a SSD with a large movie/tv collection.

Edited January 26, 2018 by bobwinters

[Luke 42085]

Thanks for the feedback.

[thynan 6]

I also noticed that harddrive-speed can have a major impact on emby performance. I had problems with veeery long loading times when browsing, and the search feature was practically unusable because it was so slow. I really didn't think it could be a disk related issue and I tried everything else to speed it up. But what finally solved the problem was just moving the entire emby data folder into a ramdisk. Now it's lightning fast. 

 

I think that maybe the combination of sqlite + big collection + standard hdd with not the fastest response time which causes trouble. 

[snorkel 15]

Sqlite can be very fast, I wonder if emby turns on the SQLite write ahead logging feature,? it really makes a difference.

Another thing is if Emby has the Nagle algorithm enabled in their TCP/IP code, if emby is sending lots of smaller packets, having Nagle enabled will cause poor tcp/ip performance.

Edited January 26, 2018 by snorkel

[snorkel 15]

Here is a link on how to disable Nagle on your system globally:

 

https://www.electronicproducts.com/Programming/OS/How_to_optimize_Windows_10_for_gaming.aspx

 

Be advised you normally do this on a per socket basis for the server listener, if you have other server services  on the machine depending on what kind of data

they send it could affect performance.

Edited January 26, 2018 by snorkel

[Luke 42085]

Sqlite can be very fast, I wonder if emby turns on the SQLite write ahead logging feature,? it really makes a difference.

 

yes we do.

[kanipek 230]

Here is a link on how to disable Nagle on your system globally:

 

https://www.electronicproducts.com/Programming/OS/How_to_optimize_Windows_10_for_gaming.aspx

 

Be advised you normally do this on a per socket basis for the server listener, if you have other server services  on the machine depending on what kind of data

they send it could affect performance.

Disabling Nagle's algorithm worked for me.

 

I began to see a lot of lag with Emby - videos played via a Shield were taking a LONG time to start playing (direct play) where before they began immediately. I am not sure what change caused the issue - I switched to the beta branch for the server about that same time, any number of Microsoft updates could also be the culprit.

 

I did some digging and ran across a few references (including this one!) to Nagle's Algorithm possibly causing issues - it was a simple enough thing to try and solved the issue immediately. Been a few days now and no further repeat of my issue.