Lemmy Server Performance

419 readers

1 users here now

lemmy_server uses the Diesel ORM that automatically generates SQL statements. There are serious performance problems in June and July 2023 preventing Lemmy from scaling. Topics include caching, PostgreSQL extensions for troubleshooting, Client/Server Code/SQL Data/server operator apps/sever operator API (performance and storage monitoring), etc.

founded 2 years ago

MODERATORS

RoundSparrow@lemmy.ml

RoundSparrow@bulletintree.com

lemmy-ui seems to be doing database search for Post Title matches while typing every single character or edit, for performance reasons suggest an option to disable this feature be available to admins (lemmy.ml)

submitted 2 years ago* (last edited 2 years ago) by RoundSparrow@lemmy.ml to c/lemmyperformance@lemmy.ml

2 comments fedilink hide all child comments

My concern is that Lemmy is not scaling and was not tested with enough postings in the database. These "nice to have" slick UI features might have worked when the quantity of postings was much smaller, but it puts a heavy real-time load on the database to search postings that keep growing in table size every day.

I also suggest that this kind of feature be discussed with smartphone app and laternate webapp creators - as it can really busy up a server dong text pattern matches on all prior posting content.

top 2 comments

sorted by: hot top controversial new old

[–] poVoq@slrpnk.net 2 points 2 years ago

Until a in memory search backend like Meilisearch or Elasticsearch is implemented this seems indeed like a very bad idea. I guess they wanted to do that and got sidetracked?

[–] RoundSparrow@lemmy.ml 2 points 2 years ago

Another performance concern I have is the tracking of per-user messages being new. I haven't traced through the code to see how this is being done. Is the database tracking every posting and/or comment that a user is reading, or is this just browser storage? Performance being my concern here if it's the server doing the work. Anyone know?