this post was submitted on 02 Jul 2023
130 points (97.1% liked)
Asklemmy
43947 readers
647 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
Thanks!
Can we pick your brain on this?
For a big instance getting an over-sized user base ... roughly how many would that be and what could the instance do about it? I'd imagine a number of infrastructural things could be done before the core lemmy code base and design needs to be substantially changed or redesigned. Big separate database service, big beefy primary server/instance or even a cluster like kubernetes (which is what mastodon.social use AFAIK).
As for the alternative where many users are distributed more even across many instances, how well would that or can that scale with all of the community data that would need to be synced up between all the instances? From what I've gathered, it's precise this kind of work that's plagued lemmy.world somewhat and caused some of the issues that users have been having, largely, it seems, from the server being overloaded with "federation workers" timing out.