2024-06-15, 09:50 AM
(This post was last modified: 2024-06-15, 09:51 AM by 21tc_sea. Edited 1 time in total.)
(2024-06-12, 04:42 PM)TheDreadPirate Wrote: Docker stats for my test instances.So this is where the problem lies! My library.db is 3.5GB, and my Jellyfin container, without any memory limit, is now occupying 15GB. If your library.db is as large as mine, I guess you would also encounter the same awkward situation as me, having to wait a long time for it to finish starting up!
Code:CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
46849591f45b jellyfin-stable-testing 0.01% 953.9MiB / 31.09GiB 3.00% 0B / 0B 1.63GB / 1.06GB 21
e1db2e291ed3 jellyfin-unstable 0.01% 640.9MiB / 31.09GiB 2.01% 0B / 0B 3.59GB / 3.41GB 17
My stable testing instance has the same library as my production instance, memory stats for my production instance below (package install in Ubuntu).
Code:chris@rat-trap:~$ ps -p 3816 -o %cpu,%mem,cmd
%CPU %MEM CMD
0.4 2.5 /usr/bin/jellyfin
2.5% of 32GB is ~820MB.
My library.db size for 250 movies, 4400 episodes, 4200 songs, 64 audiobooks, and 500 music videos is 107MB.
Code:chris@rat-trap:~$ ll -h /var/lib/jellyfin/data/library.db
-rw-r--r-- 1 jellyfin jellyfin 107M Jun 12 10:12 /var/lib/jellyfin/data/library.db
And the metadata directory is 14GB.
Code:chris@rat-trap:~$ du -sh /var/lib/jellyfin/metadata/
14G /var/lib/jellyfin/metadata/