BloodyIron 24 Posted February 5, 2018 Posted February 5, 2018 Hey Devs, Some of you may know, I recently switched to the .NET Core version of Emby. More specifically, I'm on 3.2.70.0, and this is on Ubuntu Linux. Within the last week/two, scanning of library folders seems to be inconsistent in terms of how long it takes. Nothing has changed in regards to infrastructure within the last multiple months. I have 3 Libraries. One for Movies, one for "Syndications & TV" and one for Music testing (I have just one album in this one). Not entirely sure what the root cause is here, as I'm not seeing any bottlenecks in the rest of my infrastructure (no network bottlenecks, no storage bottlenecks, and monitoring doesn't suggest other possible causes). As of this writing, the VM is using 1.47GB/4.84GB of available RAM, with 14.4MB of swap being used. So that suggests it's not a memory problem either. I suspect you'll want me to toss you lovely folks a server log, and that's fine. If you do want me to do that, is there any particular things you want me to do, or steps you want me to take, BEFORE I submit the logs? Please advise, as I know you folks have repeatedly been trying to improve Library scanning, and it has been improving! Just this recent behaviour is odd.
Luke 42086 Posted February 5, 2018 Posted February 5, 2018 Hi there, please discuss an example and attach the information requested in how to report a problem. thanks. 1
BloodyIron 24 Posted February 5, 2018 Author Posted February 5, 2018 I may have actually identified the cause. One of the series that I have was not being accurately identified. Logs gave me the IMDB number, looked it up, and then got the TVDB number for it. I tried identifying the series by typing in part of the name, but it didn't quite come up with the correct one. The solution was typing in the TVDBID in the identify form. The show is : https://www.thetvdb.com/?tab=series&id=328519 Once the series was correctly identified, I got images and other meta stuff successfully for it. Library scan time dropped to ~28 seconds. So far this looks to have solved it. Not sure why the identification was wonky... hmmm... @@Luke Do you still want me to file a report or anything?
BloodyIron 24 Posted February 5, 2018 Author Posted February 5, 2018 Thanks! Is there anything more I can do to help with this situation/problem? I'm not sure if you want any more info from this instance. I know it is resolved, I just don't know if my help is worthwhile at this point, or do you have all the useful info? Well done.
Luke 42086 Posted February 5, 2018 Posted February 5, 2018 If it comes up again then let's take a closer look at it, thanks.
BloodyIron 24 Posted February 5, 2018 Author Posted February 5, 2018 Roger that! If it comes up again then let's take a closer look at it, thanks.
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