this post was submitted on 02 Jul 2023
66 points (94.6% liked)
Asklemmy
43393 readers
1394 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[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
I'm pretty damn sure its physical lack of compute, because lemmy.ml already massively upgraded their server two weeks ago to account for this, and it's already overloaded again.
Also, this was an issue early on in Mastodon as well. The more federated servers there are, the more each server has to communicate with every other server which apparently eats up RAM and CPU cycles. So each time there's an update, it has to sent it to X number of servers, and retrieve data from X number of servers, and as X climbs, the more network activity and CPU cycles to handle it there is. A lot of requests in waiting can be stored away in RAM, but even RAM has limits.
Finally, the newest server version was supposed to help ease this kind of stuff by moving from using WebSockets to HTTP. Pretty sure the federation protocols are all just HTTP, but I could be wrong.