we accidentally did the upgrade just now, which is what you just experienced. anyways we’re at like double the power and processing, and three times the storage we were previously at so yeah hopefully that’ll be good. anyways i guess i’ll leave this post stickied until i go to sleep in like an hour

    • alyaza [they/she]@beehaw.orgOPM
      link
      fedilink
      English
      arrow-up
      41
      ·
      1 year ago

      oh god hopefully not with what we’re running now lol, we’ll see on the 12th i guess but for some perspective we can probably handle traffic of three to five times the intensity of what we did today (eyeballing it) based on just the metrics i can quickly reference now (i am not our tech person)

      • lemmyng@beehaw.org
        link
        fedilink
        English
        arrow-up
        18
        ·
        1 year ago

        Would it be worth adding a CDN (eg cloudflare or fastly) as a preventative measure? I don’t know what your traffic distribution is between static and dynamic content, but i imagine being able to offload image GETs would at least prevent you from getting surprise egress traffic bills.

        CF also has an “always online” feature to serve a cached version of the site of the server is down. It won’t allow people to post it comment, but it might provide a smoother user experience.