mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-24 07:30:57 +01:00
Reduce hard disk access during playback #3795
Labels
No labels
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
EFjellyfin.db
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: starred/jellyfin#3795
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @d3f113 on GitHub (May 1, 2022).
It is amazing how hard my NAS is working during playback. Plex on the other side has nearly no hard disk activity. It would be great, to reduce it.
Besides that, Jellyfin is quite nice, even if it has some bugs :)
@elgabo86 commented on GitHub (May 2, 2022):
Have you noticed this problem with transcoding or direct play?
@jellyfin-bot commented on GitHub (Aug 31, 2022):
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.
@gbakeman commented on GitHub (Sep 2, 2022):
I'd like to jump in on this issue since it has been affecting me for quite some time as well. On Jellyfin 10.8.4 in docker. I've only opened the server from a web browser and attempted to look at my library when the performance issues hit. Jellyfin appears to be maxing out my disk I/O (which to be fair, is not much) and it's causing the entire system to choke. It's not entire clear what exactly Jellyfin is doing (I wish this was shown somewhere in the dashboard), and the logs aren't terribly helpful with lots of delayed HTTP response errors indicating the slowdown.
@Shadowghost commented on GitHub (Sep 3, 2022):
Do you save your artwork alongside your media?
Because Jellyfin does not cache local artwork but instead directly loads it from the respective directory
@gbakeman commented on GitHub (Sep 3, 2022):
It looks like I have "Save artwork into media folders" unchecked. I've since rebooted the entire operating system that was hosting docker & Jellyfin, and suddenly it's responding incredibly fast. No idea why that would've fixed anything... In the future though, it would be nice if we could see what the Jellyfin backend was doing on our dashboard.
@jellyfin-bot commented on GitHub (Mar 19, 2023):
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.