Changing posters on this brand new install doesn’t affect loading times as significantly as it did on the older one however the time for the XML to load went from <100ms to 1.5s. So still a large increase relatively.
The only change between refreshing the XML page was updating the poster.
I’m happy to forward this DB as well, if it helps.
I checked the taggings table for this newly scanned in database and it doesn’t seem like the tag_id is static. On this database the tag_id for the artwork is 107225 and 107224.
So 100 and 101 don’t seem to mean anything in particular.
Is there any answer as to why just changing a simple poster is making the file basically unplayable? Carousels example above shows what it’s doing in the background on just a simple poster change from the Edit screen.
well, but where is the size limit? I mean I have a library of only 250 movies and it is also slow/exhibits slow loading… Again if you also need my DB - I´m happy to provide it.
250 movies in one library and 920(ish) in a different library, that do have “references” between them. One lib is a lib containing 4K versions of the movies and the 2K files are in the other lib.
Not many TV shows, some other libs only contain trailers and other vids. (that should not have any cross-references)
I don’t know why they put things in there. I’m not a DB/Server expert on the design.
If this can be confined to the Plex Movie Agent, and recreated with a small DB.
(My initial test of 20 movies did not recreate the problem) then we have something for the engineer to work with.
I’ve looked at tag counts in individual movies so far. There is no obvious correlation.
My focus is to figure out how to easily recreate the problem with the smallest dataset and submit it for eval & resolution.
For instance, on my database where nearly every movie was non-functional running this sqlite fixed the issue immediately.
sqlite3 com.plexapp.plugins.library.db "DELETE FROM taggings WHERE tag_id IN (SELECT tag_id FROM taggings WHERE text LIKE '%image.tmdb.org%' OR text LIKE '%artworks.thetvdb.com%' OR text LIKE '%metadata-static.plex.tv%');"
The same amount of episodes are in this database. The ONLY difference is removing the excess entries in the taggings table.
I suppose this might only present itself on a somewhat large library, as even with dozens of useless rows that table is still relatively small with only 20 items.
Just as a further example, using Toy Story 4 again as an example. There are over 160 different art URL’s for various backgrounds etc. (This is AFTER changing the poster in the UI).
Toy Story 4 will take 15+ seconds to load, if it does at all.
If you delete these 160 art entries, nothing changes with the item visually but playback is nearly instant.
Here’s the contents of taggings for the metadata_item_id 366205. None of these seem neccesary. Deleting them causes no apparent issues and restores load times.
Toy Story 4 would load most of the time.
Other times, “There was an error editing…”
In looking at the DB, not sure if it’s how I created it or not, the tag_id is 165.
When I run counts on this database:
select count(*) FROM taggings WHERE tag_id IN (SELECT tag_id FROM taggings WHERE text LIKE '%image.tmdb.org%' OR text LIKE '%artworks.thetvdb.com%' OR text LIKE '%metadata-static.plex.tv%');
251004
sqlite>
That’s 10% of the taggings table total count.
I have taken this info to engineering and asked for more guidance on how to isolate further for them OR if what I have here is enough