Jump to content

issues opening Emby for WMC - kinda slow


rliepins

Recommended Posts

rliepins

Hi all

 

I have been having a performance issue opening Emby for WMC now for a while.  When I first call Emby in WMC, it takes 15 seconds or so before I finally get presented with my Emby page.  I have taken a look at the log in MBClassic log file in the ProgramData/MediaBrowser-Classic/Logs directory.  I can pinpoint where in the log it hangs before continuing.  Would you please have a look at this snippit and let me know what might be the issue?  There is a debug line at the 2015-12-28 11:37:20.3873 mark which I am curious about and am wondering if it is a certificate issue.

 

--------------------------

2015-12-28 11:37:03.2283,Info,,Server version: 3.0.5781.8,1,Application
2015-12-28 11:37:03.2803,Debug,,GoToPage: resx://MediaBrowser/MediaBrowser.Resources/SplashPage,1,Application
2015-12-28 11:37:03.5163,Info,,Sending Http Get to http://192.168.19.210:8096/mediabrowser/System/Info?format=Json,1,Application
2015-12-28 11:37:20.3223,Info,,Sending Http Get to http://192.168.19.210:8096/mediabrowser/Plugins?format=Json,1,Application
2015-12-28 11:37:20.3873,Debug,,=========System looking for assembly: MediaBrowser,, Version=3.0.281.0,, Culture=neutral,, PublicKeyToken=59fc04479785fd64,1,Application
2015-12-28 11:37:20.3873,Info,,Plug-in reference to MediaBrowser,, Version=3.0.281.0,, Culture=neutral,, PublicKeyToken=59fc04479785fd64 is being linked to version 3.0.292.0,1,Application
2015-12-28 11:37:20.3893,Debug,,Added Plugin assembly: Chocolate,, Version=3.0.8.6,, Culture=neutral,, PublicKeyToken=cbacf2b624ff6ad4,1,Application
2015-12-28 11:37:20.4463,Debug,,=========System looking for assembly: MediaBrowser,, Version=3.0.241.0,, Culture=neutral,, PublicKeyToken=59fc04479785fd64,1,Application
2015-12-28 11:37:20.4463,Info,,Plug-in reference to MediaBrowser,, Version=3.0.241.0,, Culture=neutral,, PublicKeyToken=59fc04479785fd64 is being linked to version 3.0.292.0,1,Application
2015-12-28 11:37:20.4513,Debug,,Added Plugin assembly: Square,, Version=1.13.13.0,, Culture=neutral,, PublicKeyToken=null,1,Application
2015-12-28 11:37:20.4913,Debug,,=========System looking for assembly: MediaBrowser,, Version=3.0.243.0,, Culture=neutral,, PublicKeyToken=59fc04479785fd64,1,Application
2015-12-28 11:37:20.4913,Info,,Plug-in reference to MediaBrowser,, Version=3.0.243.0,, Culture=neutral,, PublicKeyToken=59fc04479785fd64 is being linked to version 3.0.292.0,1,Application
2015-12-28 11:37:20.4963,Info,,Subdued - Creating Theme,1,Application
Link to comment
Share on other sites

Looks like it is taking 20 seconds to get the top library items from your server.  If you close out and go right back in, is it faster?

Link to comment
Share on other sites

perpetual98

I've been having an issue lately too on one of my HTPCs with emby taking a while to open from WMC.  Lately it's been taking (with my super accurate head stopwatch) around 2 minutes to open after I click it in WMC.  Brand new Windows 7 install too.  I nuked that PC thinking I had some other unrelated issues, but emby is still dreadfully slow.  Server and client on the same PC.  Older dual core Pentium with 3GB of RAM, but I don't think it's hardware related because it was running fine for a long time.

Link to comment
Share on other sites

I'm having this on windows 10, put it down to the hacked nature of WMC tbh... @@ebr you want logs or is w10 notably problematic??

Link to comment
Share on other sites

perpetual98

Looking at a log file, it looks like my client is trying to find a server that doesn't exist and keeps timing out before it finds the actual server at 10.101.  I will keep digging to see if I can figure out why it's looking for something that doesn't exist.

Link to comment
Share on other sites

Looking at a log file, it looks like my client is trying to find a server that doesn't exist and keeps timing out before it finds the actual server at 10.101.  I will keep digging to see if I can figure out why it's looking for something that doesn't exist.

 

Because you configured it to go directly to that server at some point.  Go into the advanced config page and switch it to find the server automatically.

Link to comment
Share on other sites

rliepins

Looks like it is taking 20 seconds to get the top library items from your server.  If you close out and go right back in, is it faster?

 

Hi.  Yes, when I close and go back in, it is faster.  I reboot my HTPC/Emby server every night, so I'm not sure if items and libraries need to reload each time...

Link to comment
Share on other sites

rliepins

Looks like it is taking 20 seconds to get the top library items from your server.  If you close out and go right back in, is it faster?

Ah....thats the clue.  I had my photos set up as a library.  There was some 300GB of photos being indexed, I assume.  Removing that library fixed that delay!  Removing this library sped up access across the board to my web client and iOS client as well.

 

Is there a way to cache a library index rather than having to reindex it each WMC start?  

Link to comment
Share on other sites

I don't think it had anything to do with the EMC start as it was the server causing the delay.  I believe it would have been quicker on a subsequent start-up of EMC.

Link to comment
Share on other sites

  • 5 months later...
perpetual98

Because you configured it to go directly to that server at some point.  Go into the advanced config page and switch it to find the server automatically.

 

I'm back to having emby look for a server at 1.101 when the server is at 1.147.  I don't see anything in the settings to tell it where the server actually is.  Is it possible to just nuke everything and start over again, or is there an easy fix to clean up a config file or something?

Link to comment
Share on other sites

Just go into the advanced config page and tell it to find it automatically.  Then set a fixed IP address on your server machine so it won't change.

Link to comment
Share on other sites

perpetual98

Just go into the advanced config page and tell it to find it automatically.  Then set a fixed IP address on your server machine so it won't change.

 

I think it was set to automatic (I'm not home at the moment) and I will set a static IP the next time I get a crack at that machine.  Is there a way to clean up the fact that it's looking at multiple IP addresses?  TIA

Link to comment
Share on other sites

It isn't looking at multiples per se.  It tries to connect to the one you have it configured for and, if that fails, it falls back to automatic detection.

Link to comment
Share on other sites

  • 5 months later...
perpetual98

This issue popped up again this week when I replaced my router at home and it started handing out new IP addresses on a 0.xxx net instead of a 1.xxx net.  I realize that it probably shouldn't matter but now it's taking 2 or 3 minutes to open Emby in WMC again.  When I used to click the icon by the clock it would bring up a browser window at 192.168.1.110:8096 and now it's bringing up localhost:8096 which should be fine, but it seems to be hunting for something prior to opening in WMC.  I have it set to Find Automatically as far as I can tell.  Is there a way I can flush the cache or something like that and have it rebuild?

Link to comment
Share on other sites

Set the start up behavior to "Show Login Screen" as well as the server to find automatically.  Then restart and you can re-configure auto login if you want.

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...