Jump to content

Lag finding media after a restart


Dignow

Recommended Posts

Dignow

I'm not necessarily sure if this is a problem that can be fixed but it is one that has been getting worse for me.  Every time I have to restart the server software the time between the restart and when I can actually use emby is growing.  At first it may have been up to 15-20 minutes but now it is easily pushing over 120 minutes.  Which can put a quick end to movie night.  I'm running server Version 3.0.5621.4. and generally connect directly through the web app on my local network.  I've attached my last two server logs.  The larger one was taken right after a restart.  The smaller about two hours later - with emby still showing zero media of any type.  I have just shy of 5000 movies, 400+ TV shows, and a few thousand albums so I understand it taking a few moments but two hours or more is unreasonable.  Another possible impact on the issue is that I recently turned Cover Art back on but it has routinely caused problems in the past.  It seems to cause out of memory exceptions and the occasional unhandled exception.  I say that only due to the fact that when I'm not using it I don't have those issues.  I've just turned it off again to see if that corrects the lag issue but I would be surprised if it did.  Finally, while the server is trying to find my media I also can't access the 'scheduled tasks' tab - there is literally nothing on the page but the headers at the top.

 

55681d3db0c1e_Capture1.png

So, I've just uninstalled cover art and restarted.  If things progress as they have before I should be able to watch something sometime later this afternoon.  Any thoughts or suggestions are most welcome - I'm really hoping this isn't just how long it will take the server to find my media.  Thanks!

 

server-63568486881.txt

server-63568467918.txt

Link to comment
Share on other sites

 I have just shy of 5000 movies, 400+ TV shows, and a few thousand albums ... I recently turned Cover Art back on but it has routinely caused problems in the past.  It seems to cause out of memory exceptions and the occasional unhandled exception. 

 

I don't think CA is actually causing the OOM issues, it is just that it is the "straw that breaks the camel's back" in memory consumption with that many items.  You should investigate applying the 64bit executable hack to the server to see if it helps you (assuming you are on x64 windows).

 

It is possible that will help your scan times as well (but that is a shot in the dark).

Link to comment
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...