2024-06-11, 03:04 AM
(2024-04-23, 04:40 AM)21tc_sea Wrote: Hello everyone!
I've been running containers for both Jellyfin and Emby using Docker and have mounted the same media library to each. I am working with Jellyfin version 10.8.13 and Emby version 4.8.0.56. After starting the containers, I encountered a couple of issues with Jellyfin that I'm not sure how to resolve and would greatly appreciate any help or guidance from the community.
The first issue is that the Jellyfin container takes a considerable amount of time, around 10-20 minutes, to start up and allow access to the web page. In contrast, the Emby container with the same media library only takes about a minute. I checked the Jellyfin logs and noticed that it always seems to pause at a specific point during startup for a long time before it continues to log output. I've captured a screenshot at this stage to share with you all, hoping someone can help me understand what's happening during this time. What could be causing this delay, and is there an effective way to speed up the process so that Jellyfin can reach the home page as quickly as Emby does?
The second issue is the discrepancy in memory usage between the two. Upon startup, Jellyfin's memory usage is around 4GB, whereas Emby's is under 1GB. How can I address this problem and reduce Jellyfin's memory usage to match Emby's level under the same conditions? I've attached two screenshots showing the resource usage for both for your reference.
Thank you in advance for any assistance you can offer!
Hello! My Jellyfin is installed on the Synology system using a Docker container. Every time it starts, it gets stuck at the same position and takes a long time to proceed to the next step, often more than ten minutes. You can take a look at the picture I put in the attachment, pay attention to the timestamps of the two log messages. From the logs, you can see that I waited at least 12 minutes for this startup. I’ve tried various methods but have been unable to solve this problem. I’m guessing if it’s because the database file is too large. In the data subdirectory of the config directory, the library.db database file is 3.5GB. My entire system only has 8GB of memory. I used the docker stats command to observe the Jellyfin container and found that it occupies around 4GB of memory as soon as it starts. It doesn’t return memory to the system when necessary, as everyone says. It only releases when the Jellyfin container is closed. However, with the same size of the database file, the Emby container can enter the web interface in less than a minute after startup. If the configuration of the Jellyfin container remains unchanged and only a small media library is mounted, it can quickly complete the startup and enter the web interface. These two problems are really troubling. One is why the startup takes so long, what is Jellyfin doing between those two lines of log messages? The other problem is why is the memory usage so high? Is there really no solution? I look forward to everyone giving me more help! Thank you!
I apologize for my poor English, the above reply is all translated, please forgive any grammatical errors!