lemmy

github.com

Lemmy scaling/performance: Move expensive PostgreSQL triggers to scheduled jobs. · GitHub Issue #3528 · LemmyNet/lemmy

github.com

RoundSparrow@lemmy.mlBannedM to

Lemmy Server Performance@lemmy.ml · 3 years ago

Move expensive DB triggers to scheduled jobs. · Issue #3528 · LemmyNet/lemmy

github.com

Requirements Is this a bug report? For questions or discussions use https://lemmy.ml/c/lemmy_support Did you check to see if this issue already exists? Is this only a single bug? Do not put multipl...

You must log in or # to comment.

Chat

Lemmy Server Performance@lemmy.ml

lemmyperformance@lemmy.ml

Create a post

You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !lemmyperformance@lemmy.ml

Lemmy Server Performance

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.

Visibility: Public

This community can be federated to other instances and be posted/commented in by their users.

1 user / day
1 user / week
1 user / month
1 user / 6 months
1 local subscriber
447 subscribers
32 Posts
0 Comments
Modlog

mods:
RoundSparrow@lemmy.mlBanned