Hi everyone

I am pretty new to all of this, so I’m currently in what I consider my “sandbox phase” of hosting a Lemmy instance.

Before promoting my instance to others I want to ensure that it’s working as it should and federation is quick and “in sync” with the major instances.

Looking at the logs I see federation is at it and working at approx 4-8 req/s - but is there a way to speed this up?

Would more workers (and thus more cores on the server) in postgres speed things up? Or perhaps more parallel workers?

As stated I’m pretty new to this, and when searching for similar questions on lemmy/github I can’t seem to find the answer to this specific question - it’s usually implied that one should know all of this before hosting.

I’ve looked into how postgres is working, but am unsure if this is the only parameter that can be changed to speed up federation.

  • chiisana@lemmy.chiisana.net
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    In the most polite way possible: The community is not yours. The content you so badly want to extract quickly, for better or for worse, belongs to the communities on the other instances, and while your users can easily join and contribute there, that’s not what should be the sole value/reason people join your instance.

    Lemmy (and the Fediverse at larger) is intended such that like minded people can congregate and discuss on subjects that are pertinent to their interest. The right way should be to subscribe to content you intend to read, bring like minded people who are interested in similar contents you read to share your instance, and then grow organically from there.

    • kense@lmmy.dkOP
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      If a new user on my instance was able to subscribe to a comunity on another instance, and all the posts/comments/likes of that community was being fetched so it was browsable on my instance - I would see no issue.

      But as of now, if a user wants to browse content from several communities on different instances - and discover new interesting comunities on different instances - while being a user on a instance filled with "like minded users, they would need a user on all instances which hosts communities of interest to 1) discover these communities 2) view the posts from these communities.

      What you are describing are single entities of communities, which defeats the purpose of federation completely, in my opinion.