Have you just installed jellyfin? The scraping for metadata for me took days literally. And the difficult time is that during the scraping, the interface is very slow.
You can monitor the scraping/parsing progress in settings > dashboard > libraries. The libraries have a sort of circular progress bar with a percentage symbol (only visible in this view) when parsing is ongoing.
Both. How quickly a server can send a webpage with images (even if they’re small) is directly proportional to the storage mediums seeks times. The worse the seek times, the less ‘responsive’ a website feels. Hard drives are a terrible location to keep your metadata.
The server scan will search for the files, look them up and grab metadata, and then store that metadata in the metadata location. If your metadata location is the same spot as your movie, it will cause some major thrashing, and will significantly increase the scan time for jellyfin. Essentially, it gets bogged down trying to read and write lots of tiny files on the same drive, the absolute worst case scenario for a hard drive to have.
If the movies are on a hard drive, and the metadata on an ssd (or even just a different hard drive) the pipeline will be a lot less problematic.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Have you just installed jellyfin? The scraping for metadata for me took days literally. And the difficult time is that during the scraping, the interface is very slow.
You can monitor the scraping/parsing progress in settings > dashboard > libraries. The libraries have a sort of circular progress bar with a percentage symbol (only visible in this view) when parsing is ongoing.
You can significantly speed this process up by putting the cache folder on an ssd, instead of the same hard drive the videos are on.
Is that the limiting factor for the UI responsiveness? Or are you talking about the fact that the parsing and metadata querying takes days?
Both. How quickly a server can send a webpage with images (even if they’re small) is directly proportional to the storage mediums seeks times. The worse the seek times, the less ‘responsive’ a website feels. Hard drives are a terrible location to keep your metadata.
The server scan will search for the files, look them up and grab metadata, and then store that metadata in the metadata location. If your metadata location is the same spot as your movie, it will cause some major thrashing, and will significantly increase the scan time for jellyfin. Essentially, it gets bogged down trying to read and write lots of tiny files on the same drive, the absolute worst case scenario for a hard drive to have.
If the movies are on a hard drive, and the metadata on an ssd (or even just a different hard drive) the pipeline will be a lot less problematic.