jellyfin / jellyfin

The Free Software Media System
https://jellyfin.org
GNU General Public License v2.0
31.75k stars 2.9k forks source link

[Issue]: TVDB Plugin slows down library scan and webui significatly #11088

Open sebman3 opened 4 months ago

sebman3 commented 4 months ago

Please describe your bug

I have had incredibly slow library scans lasting over 2 hours, while it is happening the WebUI and entire server is slowed down and is unusable. Every page takes 10-20 seconds to load. I realized that when the TVDB plugin is disabled this is no longer an issue

Reproduction Steps

  1. have tbdb plugin enabled
  2. run library scan

Jellyfin Version

10.8.13

if other:

No response

Environment

- OS:Debian 12
- Linux Kernel:
- Virtualization:
- Clients:jellyfin for linux flatpak, swiftin for apple tv, kodi for nvidia shield
- Browser:librewolf
- FFmpeg Version:
- Playback Method:directplay
- Hardware Acceleration:none
- GPU Model:
- Plugins:
- Reverse Proxy:
- Base URL:
- Networking:
- Storage:

Jellyfin logs

*

FFmpeg logs

No response

Please attach any browser or client logs here

No response

Please attach any screenshots here

No response

Code of Conduct

felix920506 commented 4 months ago

Please provide details about your setup:

  1. Do you have the database and other Jellyfin files on a mechanical hard drive? If so please provide the exact model of the drive.
  2. Are the Jellyfin files and the media files physically on the same storage device?
sebman3 commented 4 months ago

My database is installed on an nvme m.2 and my tv shows are windows network share mounted.

They aren't on the same device

solidsnake1298 commented 4 months ago

I couldn't replicate the problem when the media is stored locally. Tomorrow I plan on trying to replicate your setup with remote storage for the media.

felix920506 commented 4 months ago

Another thing. Do you have the save metadata alongside media option enabled?

sebman3 commented 4 months ago

No I don't, the network mounts are read only

jellyfin-bot commented 4 days ago

This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.

If you have any questions you can use one of several ways to contact us.