2024-04-23, 04:40 AM
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.
![[Image: jf-start-debug.png]](https://i.postimg.cc/m2vnSm6X/jf-start-debug.png)
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.
![[Image: jellyfin-mem.png]](https://i.postimg.cc/9fVN6r2y/jellyfin-mem.png)
![[Image: emby-mem.png]](https://i.postimg.cc/pTLcd4pT/emby-mem.png)
Thank you in advance for any assistance you can offer!
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!