Lemmy

12541 readers

13 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.

founded 4 years ago

MODERATORS

nutomic@lemmy.ml

Lemmy.ml is much snappier after the recent upgrade (lemmy.ml)

submitted 5 months ago by maegul@lemmy.ml to c/lemmy@lemmy.ml

17 comments fedilink hide all child comments

This is just to followup from my prior post on latencies increasing with increasing uptime (see here).

There was a recent update to lemmy.ml (to 0.19.4-rc.2) ... and everything is so much snappier. AFAICT, there isn't any obvious reason for this in the update itself(?) ... so it'd be a good bet that there's some memory leak or something that slows down some of the actions over time.

Also ... interesting update ... I didn't pick up that there'd be some web-UI additions and they seem nice!

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

[–] poVoq@slrpnk.net 5 points 5 months ago (5 children)

Try switching to Postresql 16.2 or later.

[–] kate@lemmy.uhhoh.com 3 points 5 months ago (4 children)

What’s new in postgres?

[–] poVoq@slrpnk.net 4 points 5 months ago (3 children)

Nothing particular, but there was a strange bug in previous versions that in combination with Lemmy caused a small memory leak.

[–] kate@lemmy.uhhoh.com 1 points 5 months ago (1 children)

In my case it’s lemmy itself that needs to be restarted, not the database server, is this the same bug you’re referring to?

[–] poVoq@slrpnk.net 1 points 5 months ago (1 children)

Yes, restarting Lemmy somehow resets the memory use of the database as well.

[–] kate@lemmy.uhhoh.com 1 points 5 months ago

Hm, weird bug. Thanks for the heads up ❤️ I’ve been using the official ansible setup but might be time to switch away from it

load more comments (1 replies)