jellyfin/jellyfin.org
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.org.git synced 2026-09-03 05:40:03 +03:00
Code Issues Packages Projects Releases Wiki Activity

Update hardware-selection.md

Browse Source
This commit is contained in:
felix920506
2024-10-25 02:00:35 +08:00
parent 75cac14ad2
commit 40d008e06c
1 changed files with 9 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/general/administration/hardware-selection.md
+9 -2
View File
@@ -20,7 +20,7 @@ Some component recommendations do not change regardless of the hardware configur
- Internet Connection: At least 20mbps upload bandwidth for remote access.<sup>2</sup>
<sup>1</sup>Your largest media file times the max number of concurrent streams all your users will consume can be used as a rule of thumb for the transcoding file size. <br />
<sup>2</sup>If you have less than 100mbps of total upload bandwidth, a bandwidth limit of 70% of your upload speed for Jellyfin is recommended. This option can be found in the dashboard.
<sup>2</sup>If you have less than 100mbps of total upload bandwidth, a bandwidth limit of 70% of your upload speed for Jellyfin is recommended to avoid affecting normal internet usage. This option can be found in the dashboard.
### Hardware Encoder Quality
@@ -56,6 +56,13 @@ If you are planning to use a dedicated graphics card (including upgrading an old
Intel Drivers are much easier to install on Linux, with many distributions including them by default. If you do not need CUDA for other applications, it is highly recommended that you stick with Intel Graphics on Linux.
### Servers without GPUs
Not having a GPU is **NOT** recommended for Jellyfin. The following specs are provided for reference only, for software tone-mapping 4K content to SDR:
- CPU: AMD Ryzen 9 5950X, Intel Core i7-12700K or better
- RAM: 16GB
### Low Power Servers
For users with expensive power or running servers on battery power:
@@ -70,7 +77,7 @@ These hardware platforms might lead to a poor Jellyfin experience. Please be car
- Intel "Atom" CPUs: Intel J/M/N/Y series low power CPUs up to 11th gen use a different architecture than higher end parts, leading to subpar performance despite what their names might suggest. Please be careful about these parts when shopping for a system to run Jellyfin.
- Prebuilt NAS devices: The software environment on most Prebuilt NAS devices often causes 3rd party software to be hard to install and not work properly. They also often have low end processors that are too slow for a good Jellyfin experience (Intel Atom, Realtek ARM CPUs etc.).
- Most SBCs (Single Board Computers): Most SBCs (Including Raspberry Pis and **especially the Pi 5**) are too slow to provide a good Jellyfin experience. If You really want to run Jellyfin on a SBC, please look at models based on the following platforms: Rockchip RK3588 / RK3588S, Intel Core, Intel 12th gen N series
- Most SBCs (Single Board Computers): Most SBCs (Including Raspberry Pis and **especially the Pi 5**) are too slow to provide a good Jellyfin experience since they often lack proper support for hardware acceleration. If You really want to run Jellyfin on a SBC, please look at models based on the following platforms: Rockchip RK3588 / RK3588S, Intel Core, Intel 12th gen N series
- AMD Graphics: AMD Graphics have poor encoder quality and poor driver support. **This applies even on Linux**.
- Low end GPUs: Certain low end GPUs (eg. GT1030, RX6400) don't have hardware encoding available. These models can't be used for Jellyfin hardware acceleration.