this post was submitted on 19 Jun 2023
14 points (100.0% liked)
Lemmy
12884 readers
20 users here now
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to [email protected].
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Every complex system (and federated systems like Lemmy qualify) has more than one potential bottleneck that can become a problem in different conditions.
The goldilocks zone is where there is a medium number of medium sized instances. Then each federation message can efficiently power browse traffic for a lot of users, and no one instance gets overwhelmed with browse traffic.
In practice, this is not how networks organize. There will both be instances that are "too large" and also lots of small instances. Right now, the Lemmy network is small and federation traffic is not a meaningful bottleneck. Browse traffic is, and that's what the devs are working on. But with time, the limits of both these things can be pushed further out improving scalability of the etwork in both directions.
Makes sense, I also think the original post would make more sense if it were talking about the distribution of large communities. For instance, if there wasn't so many of the largest communities on the same 2-4 servers, then I think browsing would be a lot smoother. In addition, I think users who say care a lot more about a certain community may choose to use that other less populated server to be their home, as it is the home to that community.
(Just a thought, I have done ZERO work with federation or ActivityPub)