this post was submitted on 12 Mar 2024
32 points (100.0% liked)

Reddthat Announcements

692 readers
2 users here now

Main Announcements related to Reddthat.

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
32
Maintenance from Postgres 15 to Postgres 16 - at 00:30 UTC AND an explanation of what is happening with Lemmy.World and Reddthat, and why it affects only Reddthat! (reddthat.com)
submitted 6 months ago* (last edited 6 months ago) by [email protected] to c/[email protected]
21 comments fedilink hide all child comments
 

Edited: this post to be the Lemmy.World federation issue post.

We are now ready to upgrade to postgres 16. When this post is 30 mins old the maintenace will start

Updated & Pinned a Comment in this thread explaining my complete investigation and ideas on how the Lemmy app will & could move forward.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 5 points 6 months ago* (last edited 6 months ago) (1 children)

I thought Lemmy supported horizontal scaling for federation activities.

Wondering how many instances of the federation server reddthat is running and if increasing the number does anything for the issue.

Edit: It seems that 0.19 started synchronizating activities, so horizontal scaling is out of the question.

https://github.com/LemmyNet/lemmy/issues/4529

[–] [email protected] 8 points 6 months ago (1 children)

It does. But only outbound. So we have 2 containers for federating outbound. It splits the list of servers in 2. Then each process sends out the queries. This is good for when you have a lot of servers federating with you.

But currently when accepting activities from 1 instance it is only 1 thread and it is only sequential/chronological order.

[–] [email protected] 4 points 6 months ago

Just FYI, I have suggested to the moderation team of [email protected] to consider moving the community to another instance so that you guys can still participate.

The technical issue might still be there, but I guess that can be a way to avoid overworking LW