Lemmy locks up and uses a lot of ressources after about a week
Had this happen 2 times already and increasing the max memory seemed to fix it. Does lemmy need that much ressources or am I doing something wrong? I'm on the latest stable version
Syndicated from the fediverse. Read and engage on the original instance.
View original on feddit.deView original on feddit.de
7 replies
Did you tune your postgres for your ram size?
I might havent done that. dont remember anymore
4gb is not a lot for a db. And it has to share it with lemmy and pictrs. It might not be enough with the standard config. Even then it might struggle if you subscribe to a lot of communities. You have to remember that every instance replicates everything the users are subscribed to. I am not sure though because my server hosts several applications and I have enough RAM.
Yea, there’s no where near enough RAM in that system. Add RAM and I’d bet everything fixes itself for a bit.
I'm running mine on a VPS with only 2.5 GB of ram and a few other smaller containers and have room.
I'd agree with the others about checking your postgres mem config.
Are there any logs from the container(s) when it locks up?
I'm a Linux/selfhosting novice, but from what I understand, Linux (and proxmox) uses intelligent resource management. It should adjust CPU and memory demands between tasks and VMs. My small stack of VMs running a media server and omv is basically always redlining with memory, occasionally with cpu (I don't have a dedicated GPU for encoding though)
The storage is a different problem, but it doesn't surprise me that Lemmy would use quite a bit of storage with active federation and multiple users.