inkubux 7 Posted November 7, 2017 Posted November 7, 2017 Here is another one with Debug Logs enabled. Log3.txt
inkubux 7 Posted November 9, 2017 Posted November 9, 2017 (edited) I resolved the issue by vacuuming the library database; https://sqlite.org/lang_vacuum.html The web interface is now snappy as it should be. It would be a good idea to set them to auto_vacuum or to create a task to do it periodically I hope it helps someone Edited November 9, 2017 by inkubux
Luke 42077 Posted November 9, 2017 Posted November 9, 2017 What kind of hard drive is emby installed on?
inkubux 7 Posted November 9, 2017 Posted November 9, 2017 (edited) What kind of hard drive is emby installed on? It is installed on my Unraid Nas with the official docker image My Hard drive is a WD Black 7200 RPM My server is a modest JQ1900 Quad core CPU but it does a good enough job at keeping everything speedy on the server side. Edited November 9, 2017 by inkubux
Buckaroo 6 Posted December 21, 2017 Posted December 21, 2017 Guys, Despite having a pretty beefy dual Xeon E3 system with 64 GB of RAM, I was having a tremendous amount of slowdown with my UnRAID Emby Docker container for several months, and it just kept getting worse. Deleting VMs, removing and throttling individual Docker containers would help briefly, but nothing seemed to solve it for long. UNTIL, that is, I discovered CPU pinning. Here's a great video guide. Note it covers both pinning Docker containers and VMs After some playing around with pinning, I was able to effectively give Emby near-exclusive use to about 1/4 of my available vCPUs and divide the rest between the UnRAID OS, a Win 10 VM and all of my other Dockers. Since I did this, performance on my Emby Docker has been great, regardless of what else might be going on. I recommend trying this before attempting hardware upgrades or destructive changes to your UnRAID system. A few tips: UnRAID likes to use the lower-numbered physical cores. In general, keep your Docker containers pinned off of them If you have a hyperthreading CPU, it's critical that you pair the correct virtual cores. Easy trick: look at the Dashboard screen under system status, which will show you the pairs and their vCPU numbers. You don't have to make it exclusive, but I'd recommend not sharing UnRAID with any VMs or Dockers that compress or decompress files.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now