Lemmy Server Performance, two birds with one stone, mass deletes of content: Account Delete, Community Delete, User Ban - moving these operations to a linear queue and add undo support / grace period

RoundSparrow@lemmy.mlM to

Lemmy Server Performance@lemmy.ml · 1 year ago

A general description of the proposed change and reasoning behind it is on GitHub: https://github.com/LemmyNet/lemmy/issues/3697

Linear execution of these massive changes to votes/comments/posts with concurrency awareness. Also adds a layer of social awareness, the impact on a community when a bunch of content is black-holed.

An entire site federation delete / dead server - also would fall under this umbrella of mass data change with a potential for new content ownership/etc.

You must log in or register 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.

0 users / day
0 users / week
5 users / month
3 users / 6 months
1 local subscriber
1 subscriber
41 Posts
0 Comments
Modlog

mods:
RoundSparrow@lemmy.ml