After moving from lemmy.ml to programming.dev, I’ve noticed that web responses are fulfilled much more quickly, even for content on federated instances like lemmy.ml and lemmy.world.
It seems like this shouldn’t make such a big difference. If a large instance is overloaded, it’s overloaded, whether the traffic is coming from clients with accounts on that instance or from other federated instances.
Can this be explained entirely by response caching?
You must log in or register to comment.
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
- !lemmy411@lemmy.ca: a community for finding communities
Icon by @Double_A@discuss.tchncs.de
- 0 users online
- 233 users / day
- 946 users / week
- 2.44K users / month
- 5.59K users / 6 months
- 1 subscriber
- 3.07K Posts
- 119K Comments
- Modlog
Yes, caching. When you ask for a remote community it doesn’t go fetch it right then. In fact, it doesn’t fetch at all. The remote community pushes when there is new data.
Caching is definitely part of the answer. Another answer I saw recently is that the Admins of an instance called Programming.dev are pretty likely to know what they are doing lol