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!

  • Marduk@hammerdown.0fucks.nl
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 years ago

    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.

    • bakavic@latte.isnot.coffee
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 years ago

      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?

      • Saik0@lemmy.saik0.com
        link
        fedilink
        English
        arrow-up
        3
        ·
        2 years ago

        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.