I’m the sysadmin for beehaw.org and our user-base has almost tripled in 24 hours. Our site has been crashing so much over this time period.

We do have some volunteers that are trying to figure out a reasonable solution for when this happens again four weeks from now.

Do you have any recommendations?

  • nick@campfyre.nickwebster.devEnglish
    1·
    1 year ago

    I made a kubernetes deployment for my lemmy service + use object storage for image hosting. Everything lemmy-side looks like it should scale fine. I’m not doing open registrations though, so it won’t impact me. The key bottleneck in my case is the database, but if need be a larger node can be provisioned to let the DB expand a bit.

    I think for larger instances some form of server-abstraction will be useful for scaling (i.e. k8s, cloud run, EKS, etc.)

  • nutomic@lemmy.ml
    0·
    1 year ago

    So far there are no major problems. Disk was filling up but probably unrelated. I guess beehaw grew a lot more in terms of percentage than lemmy.ml during this time.

    The main things I can think of which might help are to increase database pool size (in config file) and number of federation workers (/admin). Also create a swapfile if you are running low on RAM.