Suggestion for "relay" Lemmy instance for personal use?
Suggestion for "relay" Lemmy instance for personal use?
I've been in Lemmy for a month and I'm quite enjoy using the service.
However, after the mass migration on both Reddit and Twitter, I feel like the services are now significantly slower than they used to be. So I'm wondering whether I should have some kind of personal CDN/relay service for "caching" information especially medias or just create a new instace and federated to public Lemmy instance?
FYI, I have a private OpenVPN served on DO and 1L "server" that run Proxmox for existing services to my home. Should be okay to have a Nginx reverse proxy, right?
You definitely could, but it's not really sustainable.
Worst case scenario: if everybody does this, and there's 50.000 subscribers on a certain community, then that community will have to update 50.000 other servers whenever one user leaves a single message or vote.
Sure, your own server wouldn't have a hard time, but it every popular server (with lots of subscribers) would. It would either take a long time for you to receive their updates, or you wouldn't get them at all.
The best thing you can do, is join a medium size server: it won't be as overloaded as a big server, and wouldn't cause as much strain on the fediverse as a personal server.
8I would think that updating 50.000 Lemmy instances would have a similar performance effect of 50.000 Lemmy users browsing one instance. In that case instance with one user won't benefit the Fedeverse, but shouldn't be an issue either.
2I would think that updating 50.000 Lemmy instances would have a similar performance effect of 50.000 Lemmy users browsing one instance.
Only if the users are browsing All their watched communities 24/7. Otherwise they would only be producing load when they're interacting with Lemmy.
4
Do you think the Fediverse would scale to a 1:1000 instance to user ratio?
0I can say with full confidence that I have absolutely no idea.
I've heard this idea thrown around before, so I take no credit for it: One way to circumvent the issue would be to have actual relay nodes. As in: nodes that don't hold contents or users themselves, but just "broadcast" incoming messages to several instances, so that the source instances don't have to. This would of course have its own drawbacks and limitations, but it would alleviate the bottleneck.
I'm sure some kind of solution will be found though. Call me optimistic, but I think the lemmi/binniverse has a bright future ahead of it. I, for one, have burned my reddit bridges.
5
I setup a server that does not store any data so as to keep browsing fast for people using it. Its at lemmy.myserv.one and you can try it. Nothing really is posted there so it’s basically just so you can no overload another instance like lemmy.world.
3Anything in particular you did so it does not store any data? I'm thinking I should try out the same on a cheap VPS.
2You font make any communities and clear the database of cached content thats no longer needed after reasonable amount of time (as its hosted on the other instances the data came from) eg: PGPASSWORD=password psql --dbname=database --username=username --command="DELETE FROM activity WHERE published < NOW() - INTERVAL '7 days';"
Does stop top month or top year since you dont have data going that far back. Obviously if you keep it then you need more disk space, memory and so on and so on.
1
I'm running my own instance with 2 users. I'm not noticing any slowdown.
1Me too, works great!
1
I’ve noticed that both Lemmy and Mastodon are slow as shit.
-1You're on lemmy.world, it's been overloaded for days.
My private instance has been as snappy as can be, everything loads instantly. That's one of the nice features is if your instance has trouble you can just use another one.
3Don't join the largest instances then. Lemmy.world is over loaded and mastodon.social is historically overloaded.
1
I’ve noticed that both Lemmy and Mastodon are slow as shit.
-3