I have a domain name that I own but am not making use of and was thinking of setting up my own personal Lemmy instance, partly so I can have a Lemmy id and instance that I can completely control, partly so that I can contribute directly to my hosting cost, and partly because it might be fun to tinker with (or it might just end up being a pain; I’m still trying to figure out which is the case).

However, from this comment it sounds like, rather than contributing to horizontal scaling and easing the load on other servers, I might actually end up increasing the load on other servers by adding yet another server that the other servers have to talk to in order to keep my server updated on the latest comments and posts to which I am subscribed.

So given this, would self-hosting a personal instance actually make things worse for everyone else and thus be an irresponsible action at this time and/or for the foreseeable future? Because the last thing that I want to do is to inadvertently add a burden to the fediverse!

7 points

Oh interesting, I’m curious on the answer to this as well.

permalink
report
reply
7 points

It’s been said here that accessing content from the large servers via a federation connection is less taxing on the servers than accessing them directly, so there’s that.

permalink
report
reply
1 point

I’m thinking this would be the case if your instance had more than 1 user subscribed to that community in the large instance - but if it is just you, wouldn’t it be similar to accessing each instance and viewing the communities there?

permalink
report
parent
reply
7 points

No. Operations like removing blocked user comments, tracking your subscriptions themselves (showing only yours when you’re on teh subscription tab), and tracking your sessions are all database heavy operations. You would be trading database heavy operations with “origin needs to send activity pub messages” to you. Activitypub messages were already being generated and is simply just also sent to you… it’s very little network traffic and that’s it.

As long as your instance views most content it receives at least once… you’re well above par for doing your work to lighten the load on the origin server.

permalink
report
parent
reply
1 point

As I understand it, there are two kinds of costs that need to be considered: the cost of viewing content, and the cost of receiving content. The first is incurred every time you access your instance and is limited to your instance, whereas the latter is incurred every time something you’ve subscribed to has received an update, and is incurred not only by your instance but also by the server hosting the community. My concern is that, while hosting my own instance would reduce the load on other servers by absorbing the first kind of cost, it would also increase the load on other servers by increasing the second kind of cost.

permalink
report
parent
reply
1 point

The former is done at the “convenience” of the publishing server, e.g. they get to it when they get to it. The latter is an on-demand response to your browser’s request.

permalink
report
parent
reply
3 points

For my personally, I’m hosting an instance so that I can play with it, but also so that I can test new functionality, and help fix issues.

So I think if you are concerned about being a burden, then actively use your instance for the betterment of lemmy!

permalink
report
reply
3 points

The impact either way is minimal, so if it is something you enjoy doing go for it. Maybe it will turn into a slightly larger instance for your friends over time and then it can have a positive impact.

permalink
report
reply
3 points

Hey that’s me!

If you’re excited, hop on, as have I! The protocol related scaling issue will resolve itself over time; a few of us are throwing ideas out and hoping some will stick with the developers.

But just bear in mind that you’re not adding to the network scaling because federation on the big servers will not be alleviated by you (or me) having an extra instance.

permalink
report
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 3.4K

    Monthly active users

  • 3.4K

    Posts

  • 77K

    Comments