If server crashes again the devs should just stop all registrations to this instance, people always follow path of least resistance and the first dev instance is just too easy to be stuck onto
Lemmy
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.
Is there anyway to scale an instance by adding more nodes? Not be adding additional instances, but more of a distributed load balancing for a given instance? What about migrating communities to a different hardware instance? What scaling challenges does Lemmy face that something like Mastondon doesn't?
I'm sure there are many folks (myself included) who have technical resources that are not community builders. I'm sure if there if there is a way to spread the load, enough folks want this to succeed to make it work.
This comment further down states that the main issue is with the heavy JOIN-laden SQL queries that build the pages; the queries get long enough that pages time out.
Load-balanced frontends for lemmy.ml would hit the same backend/DB, as I understand it, so spinning up a frontend won't necessarily help with the load. What's needed is someone who knows pgsql optimization, and that's not me. (I might be able to help if it were MySQL...)
Test
Lol yeah. I learned my lessons from using Matrix.
If now is struggling then on June 12 will be a nightmare.
Reddit will go dark in protest, many messages to join Lemmy, most instances will be overloaded or even DDoS with so many users, like what happen with Mastodon.