So after we’ve extended the virtual cloud server twice, we’re at the max for the current configuration. And with this crazy growth (almost 12k users!!) even now the server is more and more reaching capacity.
Therefore I decided to order a dedicated server. Same one as used for mastodon.world.
So the bad news… we will need some downtime. Hopefully, not too much. I will prepare the new server, copy (rsync) stuff over, stop Lemmy, do last rsync and change the DNS. If all goes well it would take maybe 10 minutes downtime, 30 at most. (With mastodon.world it took 20 minutes, mainly because of a typo :-) )
For those who would like to donate, to cover server costs, you can do so at our OpenCollective or Patreon
Thanks!
Update The server was migrated. It took around 4 minutes downtime. For those who asked, it now uses a dedicated server with a AMD EPYC 7502P 32 Cores “Rome” CPU and 128GB RAM. Should be enough for now.
I will be tuning the database a bit, so that should give some extra seconds of downtime, but just refresh and it’s back. After that I’ll investigate further to the cause of the slow posting. Thanks @veroxii@lemmy.world for assisting with that.
Oh, so it is due to the larger userbase here! There is a larger chance that someone already subscribed to a community I am looking for.
Still, when I was using another instance, subscribing to communities at lemmy.world was instantaneous while subbing to communities at beehaw.org or lemmy.ml often took more than one try.
It also doesn’t help that lemmy.ml where a lot of users migrated at first seems to be having issues right now.
Also on jerboa searching for communities by url doesn’t seem to be working.
Hopefully the influx of new users and attention helps improving and ironing some issues like it happened with mastodon.
