Any way to check in the app what is using all this ram?

[natzilla]

@girish Here you are

CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
2058a37598b0 7d771f27-4c9e-48ff-b0ff-3c742305adb3 2.28% 27.12GiB / 29.12GiB 93.14% 1.01GB / 263GB 132GB / 65.5GB 56

[girish]

@natzilla Was trying to check if we hit some parsing error in the code. Can you give me the output of docker stats --format "{{ json . }}" --no-stream --no-trunc | grep 2058a37598b0 ?

[natzilla]

@girish as requested

{"BlockIO":"171GB / 83.4GB","CPUPerc":"0.14%","Container":"2058a37598b0","ID":"2058a37598b013a36a5a3d05a362e96dc4ad212dec1d5db162e372979bc47c38","MemPerc":"84.77%","MemUsage":"24.68GiB / 29.12GiB","Name":"7d771f27-4c9e-48ff-b0ff-3c742305adb3","NetIO":"1.27GB / 410GB","PIDs":"57"}

[girish]

@natzilla So, the values in the graph come from the json you posted. Specifically "MemUsage":"24.68GiB / 29.12GiB" . (memory used / memory max) . This sort of matches what's displayed in the graph.

[natzilla]

@girish ok, it must really be using that much then. Seems pretty crazy, but I will check with Jellfin devs regarding this.

[robi]

what host are you running your VPS on?

[natzilla]

@robi Cloudron and all the apps run on a R720XD

[robi]

@natzilla I was asking who the provider was, as sometimes they have a virtualization platform that can cause this as a way to reclaim memory for the underlying host from hungry VMs, etc.

[natzilla]

@robi I'm not hosting it in the cloud. Sorry I should have made that clear.

[robi]

@natzilla ok, so it's on a bare metal server with no virtualization layer in between.

[natzilla]

@robi You are correct, poweredge r720xd

[robi]

@natzilla DELLicious. Thanks for ruling out the middleware.

Definitely points to an upstream issue not cleaning up.