this post was submitted on 11 Jun 2023
130 points (96.4% liked)
Asklemmy
43902 readers
1129 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 don't believe this is how it works though.
Let's say your tiny 3 person instance is connected to a big one. I believe it only pulls in content from the communities somebody from the small instance is subscribed too. Correct me if I'm wrong.
That's what they're saying.
Essentially - if someone from the small instance subscribes to a community that has a ton of data (huge post volume, images, whatever), the small instance needs to pull data over from the larger instance. At some point there may be communities that are so large small instances can't pull them in without tanking.
Could that be solved by caching? Can't the smaller instance avoid some duplication?
I wonder if there is a way to get around this? maybe smaller instances will have to be text-only?
maybe I phrased that poorly and you didn't understand what I was trying to say. The size of the bigger instance shouldn't matter at all because only data from communities is pulled, that a member of the smaller instance is subscribed to. So if the bigger instance has 1000 members or 2 million members wouldn't make a difference. The only thing relevant should be how active the communities are that members are subscribed to.
That's what I've gathered, but I don't believe there's a way for instance owners to limit what's fetched - a user crafts the query and the server does the needful.
I imagine this could amount to a denial of service attack of sorts, if some high-churn communities are imported into tiny instances. How bad that could be, I have no idea - I'm speaking pretty theoretically, here. Text is tiny, after all, so it's probably not much of a concern, since most of the media is actually handled elsewhere...
I'm not a web developer. I'm sort of a sysadmin so i have some experiences maintaining machines for web apps for other people. And you are right...text will not create massive amounts of data. But a lot of tiny transactions can bring down machines surprisingly fast even if the total amount of data is relatively small.
I guess we are here to experience it first hand. I don't think anybody...not even the developers have a clear idea of how well this will scale. There is only one way to find out lol