So after we’ve extended the virtual cloud server twice, we’re at the max for the current configuration. And with this crazy growth (almost 12k users!!) even now the server is more and more reaching capacity.

Therefore I decided to order a dedicated server. Same one as used for mastodon.world.

So the bad news… we will need some downtime. Hopefully, not too much. I will prepare the new server, copy (rsync) stuff over, stop Lemmy, do last rsync and change the DNS. If all goes well it would take maybe 10 minutes downtime, 30 at most. (With mastodon.world it took 20 minutes, mainly because of a typo :-) )

For those who would like to donate, to cover server costs, you can do so at our OpenCollective or Patreon

Thanks!

Update The server was migrated. It took around 4 minutes downtime. For those who asked, it now uses a dedicated server with a AMD EPYC 7502P 32 Cores “Rome” CPU and 128GB RAM. Should be enough for now.

I will be tuning the database a bit, so that should give some extra seconds of downtime, but just refresh and it’s back. After that I’ll investigate further to the cause of the slow posting. Thanks @veroxii@lemmy.world for assisting with that.

  • Luca@lemmy.worldEnglish
    1·
    1 year ago

    I’m not too familiar with Lemmy’s codebase, but I am a devops engineer. Is the software written in any way to support horizontal scaling? If so, I’d be happy to consult/help to get the instance onto an autoscaling platform eventually.

    • terebat@programming.devEnglish
      0·
      1 year ago

      Doesn’t support HA or horizontal scaling yet from what I read. Unsure if kbin does. Probably would have to add support for horizontal scaling to have that auto scaling do anything.

      • Luca@lemmy.worldEnglish
        1·
        1 year ago

        Yeah, that’s what I was afraid of. Understandable though, since horizontal scaling/HA usually isn’t a priority when developing a new application.