[PR #15724] FFProbe: Reduce probesize to 500M #14222

Open
opened 2025-12-22 10:23:17 +01:00 by backuprepo · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/jellyfin/jellyfin/pull/15724
Author: @luigi311
Created: 12/5/2025
Status: 🔄 Open

Base: masterHead: reduce_memory


📝 Commits (1)

  • d97c428 FFProbe: 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

probe_1g

Memory usage after

probe_500m

Issues
Relates to #14095


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/jellyfin/jellyfin/pull/15724 **Author:** [@luigi311](https://github.com/luigi311) **Created:** 12/5/2025 **Status:** 🔄 Open **Base:** `master` ← **Head:** `reduce_memory` --- ### 📝 Commits (1) - [`d97c428`](https://github.com/jellyfin/jellyfin/commit/d97c428b1f7b904c3c17e839697ab62dbfd4687f) FFProbe: Reduce probesize to 500M ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `Emby.Server.Implementations/ConfigurationOptions.cs` (+1 -1) </details> ### 📄 Description <!-- Ensure your title is short, descriptive, and in the imperative mood (Fix X, Change Y, instead of Fixed X, Changed Y). For a good inspiration of what to write in commit messages and PRs please review https://chris.beams.io/posts/git-commit/ and our documentation. --> **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 <img width="2803" height="611" alt="probe_1g" src="https://github.com/user-attachments/assets/16306c98-7476-444a-89d3-79223c5ca15d" /> Memory usage after <img width="2803" height="611" alt="probe_500m" src="https://github.com/user-attachments/assets/bae2059c-2b75-4194-bcb0-d82bc8bee5e4" /> **Issues** Relates to #14095 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
backuprepo added the
pull-request
label 2025-12-22 10:23:17 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: starred/jellyfin#14222
No description provided.