I’m aware that some of you have been getting some errors loading this instance. This was a configuration that I needed to be adjusted which has since been.

Do be patient if we run into other issues, I’ll be continuously working in the back-end with others to better your overall experience.

Still a lot of capacity available!

edit: For those that are interested in the configuring changes. I was using the default lemmy configuration for the nginx worker_connections value. This value needed to be raised. Shout out to @[email protected] over at lemmy.world for helping me out.

  • TheDudeOPMA
    link
    fedilink
    English
    arrow-up
    10
    ·
    2 years ago

    its not so much about how many registered users as it is about how many online users. The online user count is what adds fuel to the fire!

    • flambonkscious
      link
      fedilink
      English
      arrow-up
      4
      ·
      2 years ago

      Oh wow so it’s really the transactions per minute, not so much the baseline set of data?

      • PCChipsM922U
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 years ago

        Yeah, basically the problem is number of calls (requests) per minute. If it’s not too many, everything works fine, if it overloads, you get 500 errors 🤷.

        • can
          link
          fedilink
          English
          arrow-up
          3
          ·
          edit-2
          2 years ago

          Including calls to federated communities, yes?

          • PCChipsM922U
            link
            fedilink
            English
            arrow-up
            2
            ·
            2 years ago

            I’m not sure about that, but most probably yes, since if you post on federated communities, your username pops up as [email protected] and the post is saved on your instance (from what I know).