Lately there appears to be some issues with the instance (sometimes it is completely down and I have also been getting a lot of 504 errors) and I was wondering if this is a known issue and when it may be fixed.

  • Beto@lemmy.studioM
    link
    fedilink
    English
    arrow-up
    2
    ·
    11 months ago

    Sorry for that! For some reason CPU was randomly spiking at 100%, and that would bring the instance down.

    I just finished upgrading to the latest release (0.18.3), which has a lot of performance improvements.

    • CoffeeDev@lemmy.studioOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      11 months ago

      For some reason CPU was randomly spiking at 100%

      That would explain the issues!

      I just finished upgrading to the latest release (0.18.3), which has a lot of performance improvements.

      I figured Lemmy would improve performance over time, so I was wondering how much it would help to update.

      (0.18.2 also added some CORS stuff which makes third party web apps work better, so I was eagerly awaiting this update similarly to 0.18)

      • Beto@lemmy.studioM
        link
        fedilink
        English
        arrow-up
        2
        ·
        11 months ago

        The only problem I’ve been having with the upgrades is that I like to take a full snapshot of the instance before doing the upgrade, and that takes some 30 minutes of downtime. Maybe as the project matures we can upgrade by dumping the DB live, but right now I don’t want to risk it.

    • CoffeeDev@lemmy.studioOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      11 months ago

      the latest release (0.18.3) … has a lot of performance improvements.

      It seems to be performing much better now. I use a userscript that replaces Lemmy links with ones to your instance, and for posts it used to take a few seconds (maybe ~5 seconds, I don’t really remember) to load the new links (it has to ping the instance to find the correct link for posts, as the post ID is different across different instances) and now it only takes a second or two to do so.