SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Jellyfin - default settings should be increased (ram & disk) #960

New Issue
Closed
opened 2025-11-20 04:57:16 -05:00 by saavagebueno · 1 comment
saavagebueno commented 2025-11-20 04:57:16 -05:00
Owner
Copy Link

Originally created by @g0tmk on GitHub (Apr 22, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

jellyfin.sh

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/jellyfin.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Ubuntu 22.04

📝 Provide a clear and concise description of the issue.

The default settings for the jellyfin script are 2GB memory and 8GB disk

Jellyfin's docs specify:
-4GB memory is enough (if running headless)
-disk should be large enough for the transcode cache, which is "your largest media file times the max number of concurrent streams all your users will consume" (source)

I understand that there is no perfect choice for disk size, but 16GB seems like a reasonable compromise. The current settings leave only ~4GB available for the cache - many users will run into this wall and jellyfin will crash.

I ran into this issue and I expect others will, also, and will likely think this is the script's fault. There is at least one example here https://github.com/community-scripts/ProxmoxVE/issues/3080

🔄 Steps to reproduce the issue.

n/a

❌ Paste the full error output (if available).

n/a

🖼️ Additional context (optional).

No response

Originally created by @g0tmk on GitHub (Apr 22, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? jellyfin.sh ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/jellyfin.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Ubuntu 22.04 ### 📝 Provide a clear and concise description of the issue. The default settings for the jellyfin script are 2GB memory and 8GB disk Jellyfin's docs specify: -4GB memory is enough (if running headless) -disk should be large enough for the transcode cache, which is "your largest media file times the max number of concurrent streams all your users will consume" ([source](https://jellyfin.org/docs/general/administration/hardware-selection#shared-items)) I understand that there is no perfect choice for disk size, but 16GB seems like a reasonable compromise. The current settings leave only ~4GB available for the cache - many users will run into this wall and jellyfin will crash. I ran into this issue and I expect others will, also, and will likely think this is the script's fault. There is at least one example here https://github.com/community-scripts/ProxmoxVE/issues/3080 ### 🔄 Steps to reproduce the issue. n/a ### ❌ Paste the full error output (if available). n/a ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 04:57:16 -05:00
saavagebueno commented 2025-11-20 04:57:17 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Apr 22, 2025):

Hi, as you can understand, we can't really know how some of the apps are used and how much of resources it should get. We can only guesstimate a sensible amount to get the app installed and running.

We always go conservative on these estimates because user can always edit the container settings before installing or increase them as demand for more resources comes. In the end, these numbers are basicaly just quotas so you can always experiment and see for yourself what numbers match your workload.

@tremor021 commented on GitHub (Apr 22, 2025): Hi, as you can understand, we can't really know how some of the apps are used and how much of resources it should get. We can only guesstimate a sensible amount to get the app installed and running. We always go conservative on these estimates because user can always edit the container settings before installing or increase them as demand for more resources comes. In the end, these numbers are basicaly just quotas so you can always experiment and see for yourself what numbers match your workload.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#960
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?