Yesterday, 11:48 AM
Hi everyone,
I’m running Jellyfin on a Raspberry Pi 5, and I’m facing issues with the Web UI becoming choppy and laggy when around 8-10 users are connected simultaneously. Additionally, SSH access to the Pi also becomes slow during this time. However, the system resources seem to be underutilized, which has left me puzzled.
Current Setup:
Thank you in advance for your help!
I’m running Jellyfin on a Raspberry Pi 5, and I’m facing issues with the Web UI becoming choppy and laggy when around 8-10 users are connected simultaneously. Additionally, SSH access to the Pi also becomes slow during this time. However, the system resources seem to be underutilized, which has left me puzzled.
Current Setup:
- Device: Raspberry Pi 5 (4GB/8GB RAM)
- Media Files: All videos are pre-transcoded to x264 format to avoid transcoding load during playback.
- Storage: Videos are stored on a high-speed external SSD connected via USB 3.0.
- Network: Gigabit Ethernet connection.
- Jellyfin Version: Jellyfin.Server 10.10.3.0
- When monitoring with
htop
, the system doesn’t seem stressed:- RAM usage is under 700MB.
- CPU usage is minimal.
- RAM usage is under 700MB.
- Despite the low resource usage, the Jellyfin Web UI becomes unresponsive, and SSH sessions are sluggish.
- Are there known bottlenecks in Jellyfin's Web UI or other components that could cause lag under heavy user traffic?
- Could this be related to I/O bottlenecks, even though CPU and memory usage remain low?
- Would implementing a reverse proxy (e.g., Nginx or Caddy) to manage connections help mitigate these issues?
- Are there system-level optimizations (e.g., network stack tuning, caching, etc.) that could improve the responsiveness of the Web UI and SSH under load?
- Is there a way to profile Jellyfin’s Web UI performance to identify specific areas causing the slowdown?
- I’ve streamlined metadata processing and set up user permissions to minimize unnecessary operations.
- My primary concern is ensuring Jellyfin can handle 40-50 users simultaneously in the future, but the current performance with just 8-10 users suggests that optimization is needed before scaling.
Thank you in advance for your help!