Hi I have jellyfin installed in a VM with 24 cores and 32GiB RAM (VM also used for Docker). Whenever I attempt to play higher quality files, jellyfin crashes after a few minutes. I haven't seen it struggle with lower quality media.

Here are some logs: FFmpeg.Transcode-2024-03-24_16-11-43_d48825174d455ae3ff859d8b28582853_ce3f3ebf.log upload_org.jellyfin.androidtv_0.16.7_20240324161053_d2befd034e424a3490e7ea55af1fe1f2.log Fmpeg.Transcode-2024-03-24_16-11-38_d48825174d455ae3ff859d8b28582853_dafa4555.log FFmpeg.DirectStream-2024-03-24_16-08-12_d48825174d455ae3ff859d8b28582853_dac7115f.log

I cannot for the life of me figure out whats wrong. I've tried disabling plugins, different clients, hard resets etc, but it still crashes.

Can someone enlighten me?? :(

you are viewing a single comment's thread
view the rest of the comments

[–] walden@sub.wetshaving.social 6 points 1 year ago (10 children)

Why not in a VM? All my stuff runs in VM's.

[–] GravitySpoiled@lemmy.ml 2 points 1 year ago (8 children)

Doesn't the vm produce an overhead? More power consumption and it can't use the full capabilities of the machine?

[–] walden@sub.wetshaving.social 5 points 1 year ago (5 children)

There are many benefits to VMs. You can limit how much RAM is available to each one, so one app doesn't eat all of your RAM. Same with CPU. Virtual Machines can be backed up, uploaded to remote storage, and restored. When it's time to do a big update on your main machine (either changing OS or getting new hardware), restoring VM's is super simple compared to the alternative.

[–] KLISHDFSDF@lemmy.ml 2 points 1 year ago (1 children)

You can limit how much RAM is available to each one, so one app doesn’t eat all of your RAM. Same with CPU.

This can be done with containers and you don't get the overhead of virtualizing a whole operating system for every service/app you might be hosting.

Virtual Machines can be backed up, uploaded to remote storage, and restored.

This can also be done with containers in a more elegant way as there's no need to back up any VM/OS data.

E.g. I have a docker compose file that can nearly immediately stand up a container with the right settings/image, point it to my restored data and be up and running in no time. The best part is i don't need to back up the container/OS because that data is irrelevant.

When it’s time to do a big update on your main machine (either changing OS or getting new hardware), restoring VM’s is super simple compared to the alternative.

With the alternative you just restore your data and run docker-compose up -d. Docker will handle the process of building, starting and managing the service.

Simple example: Your minecraft server died but you have backups. You just restore the data to /docker/minecraft. Then (to keep things really simple) you just run:

docker run -d -p 25565:25565 --name minecraft -e EULA=TRUE -v /docker/minecraft:/data itzg/minecraft-server

and in a few minutes your server is ready to go.

[–] walden@sub.wetshaving.social 1 points 1 year ago

If that's the way you'd prefer to do it, I highly recommend taking that approach.

load more comments (3 replies)

load more comments (5 replies)

load more comments (6 replies)