Jump to content

Cast Lookup Crawls


WhackOBill
Go to solution Solved by d00zah,

Recommended Posts

WhackOBill

A few months back, one of the Emby upgrades (probably on the server side) caused the Cast lookup in Emby for WMC to slow to a crawl where the menu item is selected and the cast pops us about 3 minutes later.  This used to be nearly instantaneous and it almost looks like a query has lost an index that needs to be rebuilt on the server side.  The data is on an SSD and so I would not expect this type of slow performance ... and really, it use to be just fine.

 

This happens in this client but as I mentioned, it may be a server side issue ... they are on the same box.  Do I need to run some sort of database re-index routine to try and clear this up?  Is there such a mechanism accessible via the Server interface?

Link to comment
Share on other sites

I notice this as well. Before the images were only pre-fetched if you clicked on an empty person (no image), and at the same time it would get the wiki info of the cast member. Now everytime you click the cast/crew button it seems to prepopulate every image at this point. So it can be slow if there are several people missing images/metadata. It now does them all at once, rather than only if I attempt to enter an empy person should the server on demand populate it. This should revert back to how it was handled before. It was much more responsive and intuitive before.

 

Sent from my Nexus 7 using Tapatalk

Link to comment
Share on other sites

WhackOBill

How does it perform in the web app?

 

Both WEB and Theater are absolutely instantaneous.  Of course, the Cast is at the bottom of the page by default and you don't click a menu item to see it like you do in the WMC client.

 

I tested a cast lookup a few minutes ago on a random TV show in the WMC client and it went out to lunch for 77 seconds ... so not the 3 minutes, but still, it used to be lightning fast.

Link to comment
Share on other sites

WhackOBill

when did you first install your server?

 

Years ago.  I was using MB ... way, way back.

Link to comment
Share on other sites

@@Luke

 

What I mean is this, pardon my intrusion into this thread, but I believe it is the same issue that plagues the roku, at least the old official app and blue neon. These apps would use the code below to get images, and only images at first, since clicking into the cast/crew image is when metadata is required not before. When the metadata is requested for the person directly would cause the on-demand download to grab the image/metadata if the image was missing. Not when first requesting the image.

for each i in people
    imageUrl = GetServerBaseUrl() + "/Items/" + HttpEncode(i.Id) + "/Images/Primary/0"
end for

This now does an on-demand fetch for every person, when it shouldn't imo. It should just show an empty spot if the image isnt there yet. If then the user of said app went hmm.. harrison ford, and clicks the empty placeholder image for harrison ford then the sever goes and does an on-demand fetch of that person and their metadata, to show the detail screen. After the user leaves the detail screen, the app refreshes the previous cast/crew screen and updates harrison fords image, and just harrison fords image. This was far better than the alternative of having every request for an image cause the on-demand download of things to fire off. It slows down the app considerably, and causes things to hang which aren't async w/callbacks, some requests block until they get a reply and several of these in sequence have the effect of crippling the app until these all finish. Only if I navigate into that person to that persons detail screen, should it do this. Hopefully I worded this right...

 

This should explain this scenario a little better (fingers crossed). Dont get me wrong, I love the on-demand fetch of the people images, but only when I havigate into that person. Cheers. ;)

Edited by speechles
Link to comment
Share on other sites

WhackOBill

I will load the beta version up when I get home.  I see from the other thread that it seems to have solved the issue.  If it doesn't, I'll find and upload the logs as requested.  This does seems to be the answer though. 

 

And thanks for continuing to support the client within WMC.  My tuners are in this box along with the LiveTV connector (ServerWMC) and it really works quite well.  At some point I expect Emby will be able to take over these TV functions I get from WMC and I will finally be able to part ways with that platform ... as Microsoft clearly intends.

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