Community discovery on self hosted Lemmy instances
Lemmy PostgreSQL performance: comment_like & post_like tables have a lot of indexes (5 alone on comment_like), SQL INSERT is taking 0.4 seconds per upvote. Federation incoming lower priority?
Lemmy PostgreSQL - can someone please help deconstruct this INSERT SQL: INSERT INTO "comment_like"...
Lemmy_server create a local community called "/c/zzz_communities" that gets a new posting automatically when a community is created on that local instance
PSA: Lemmy 0.18 is rolling out in produciton, lemmy.ml has already been upgraded to BE: 0.18.0-rc.6 - the "websocket webapp" removal
Lemmy Wish: "trending communities" should have a dedicated page of output - with the full descriptions and Lemmy Instance hosting the community
OBSERVATION: lemmy.ml is now running BE: 0.18.0-rc.6 - not sure on lemmy-ui, but it looks upgraded. The "websocket webapp" change
I suspect the widespread Federation problems and 'nginx 500' errors are connected, Lemmy is swarming comments, likes to other Lemmy servers and causing a Denial of Service on peers
Scaling federation throughput via message queues and workers · Issue #3230 · LemmyNet/lemmy
: Established instances (not new installs), Community join/subscribe "Pending" for some busy remote servers · GitHub Issue #3203 · LemmyNet/lemmy
Lemmy server admins, please enable pg_stat_statements on your PostgreSQL server so the Lemmy community can better identify the performance problems on the more active sites
PostgreSQL "activity" table grows large: Configurable Activity Cleanup Duration · GitHub Issue #3103 · LemmyNet/lemmy
PSA: The Lemmy federation convention of hotlinking images to other peer federation servers makes it easy for a rogue instance to collect end-user IP addresses & browser strings, don't assume otherwise
Deleting a user with lots of comments (1,59k) modding a few large communities (~20) kills the backend · Github Issue #3165 · LemmyNet/lemmy
Proposal: Lemmy incoming federation data, queue to database INSERT into comments, votes and other large tables
There was a lot of advice handed out back in June that the answer to scaling Lemmy was to go create instances. The reason it works is because "All" is empty on a virgin system ;) With no data in the database, the logic Lemmy hands to PostgreSQL works real fast ;)