Lemmy.world has been down between 02:00 UTC and 05:45 UTC. This was caused by the database spiking to 100% cpu (all 32 cores/64 threads!) due to inefficient queries been fired to the db very often.

I’ve collected the logs and we’ll be checking how to prevent this. (And what caused this)

  • SpaceBar@lemmy.world
    link
    fedilink
    English
    arrow-up
    15
    ·
    3 years ago

    What’s the name of the server you are running?

    A large instance today will be a small instance in the future. There are hardly any users on lemmy compared to other more established platforms. So if lemmy is to ever handle a lot more users, stress testing the code makes a lot of sense.

    What’s going to happen in the future, do you expect there to be 50,000 servers? That’s unrealistic.

    • Yoz@lemmy.world
      link
      fedilink
      arrow-up
      1
      arrow-down
      21
      ·
      3 years ago

      You’re not taking into account that some people are dumb as fuck. They will sit on one instance and when the instance goes down , they’ll start whining