mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-23 23:20:51 +01:00
[PR #15724] FFProbe: Reduce probesize to 500M #14222
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#14222
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?
📋 Pull Request Information
Original PR: https://github.com/jellyfin/jellyfin/pull/15724
Author: @luigi311
Created: 12/5/2025
Status: 🔄 Open
Base:
master← Head:reduce_memory📝 Commits (1)
d97c428FFProbe: Reduce probesize to 500M📊 Changes
1 file changed (+1 additions, -1 deletions)
View changed files
📝
Emby.Server.Implementations/ConfigurationOptions.cs(+1 -1)📄 Description
Changes
Reduce the ffprobe probesize down from 1G -> 500M. With 500M i havent seen any warnings asking to increase the probsize or duration in the logs after doing a full scan on my movies. This brings down the average memory usage for my full movies scan down from 3.38 GB -> 2.75 GB. Should have a bigger impact for servers that are using a higher parallel scan count.
Memory usage before
Memory usage after
Issues
Relates to #14095
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.