Its now running on a dedicated server with 6 cores/12 threads and 32 gb ram. I hope this will be enough for the near future. Nevertheless, new users should still prefer to signup on other instances.

This server is financed from donations to the Lemmy project. If you want to support it, please consider donating.

  • sealneaward@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Is most of the discussion about the infrastructure done in a community here, or do you folks have an invite only discord/slack or something @nutomic@lemmy.ml?

    I’ve been working in devops for 4 years now, but with mostly kubernetes and AWS, but I’d like to throw some ideas and just ask some more specific questions about the infrastructure. Like I’m curious why autoscaling the web servers and moving the database server to a dedicated instance is not the current configuration.

    • nutomic@lemmy.mlOPM
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      There is really not much to discuss. The server was overloaded so we got a bigger one. And there is no reason to mess with stuff like kubernetes when a single server works fine. After all our job is to improve the Lemmy software for everyone, not build a huge centralized platform only on lemmy.ml.

      • sealneaward@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        1 year ago

        I agree with the kubernetes point. Not every problem needs it.

        I was more curious about having a load balancer infront of an autoscaling group of servers with the existing images that you are running off of, minus the self hosted database server. Then you would be able to handle spikes automatically. Just curious if that has been thought of.

        Having it accessible to everyone is great. For sure. But I was just thinking that having stronger pieces of infrastructure for instances that handle more traffic might be beneficial.