Lemmy instance using a lot of ram

stown , 4 months ago

I wonder if this is the cause for the UI failing and showing a white page with "server error". It has something to do with a failure to retrieve the site icon and if postgres is crashing that could explain why lemmy-ui is failing to retrieve the site icon.

My current "fix" for this is a script that runs every 10 minutes and sets the site image to NULL, curls the site URL, then sets the site image back to what it was. This does seem to work around the problem and if the UI does crash it's only down for a maximum of 10 minutes.

romano , 4 months ago

Yea, I had to make a crontab task that resets lemmy every day. Hope it gets fixed in the future but for now it sorta works.

Die4Ever , 4 months ago

https://github.com/LemmyNet/lemmy/issues/4406

youpie_temp OP , 4 months ago

oh wow thanks, ill see if that fixes it! weird that it doesnt get killed by OOM killer on my server

redcalcium , 4 months ago

Does your server has a big swap space?

youpie_temp OP , 4 months ago

It has zswap and a swapfile of about 8 gb, and it gets fully utilized

redcalcium , 4 months ago

Yeah, this is why I have small swap on my servers. I'd rather the process got killed by the oom killer and got restarted automatically instead of running very slowly and trashing the entire server when it uses too much memory.

jeena , 4 months ago

Since my upgrade to 0.19 I really struggle to keep my servr online. It sounds like what is happening to me too. The whole server beco.en unesponsive after the load goes to 100. After I kicked NextCloud from the server in only kept happening every coupple of days. Let's see if this workaround helps to fix it. If not then I'll remove swap.

poVoq , 4 months ago

I have been running a cron script to automatically restart the lemmy backend, which in turn resets the postgres memory use ever since this problem started to happen months ago. For me 0.19.x actually made it less bad, but it is still an annoying issue.

redcalcium , 4 months ago

Try limiting the database connection pool size too in lemmy.hjson. It helped a lot in my instance. I set mine to 30 in a small server with 8gb ram. You can set it to even lower value for lower postgres memory consumption.

database: {
        host: dbhost
        user: "lemmy"
        password: "secret"
        database: "lemmy"
        pool_size: 30
}