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.

you are viewing a single comment's thread
view the rest of the comments

[–] manitcor@lemmy.intai.tech 17 points 1 year ago (1 children)

do you plan to publish any of your scaling data? Some others might consider helping by running large instances and your learnings would be incredibly helpful.

[–] ruud@lemmy.world 36 points 1 year ago (1 children)

Yes, when I get around to it I can create a post about it. And of course, feel free to ask.

[–] manitcor@lemmy.intai.tech 5 points 1 year ago* (last edited 1 year ago)

if you had any basic numbers easily accessible like iops peak and average or screen shots of your dashboard showing resource utilization would do wonders. Right now you are getting slammed but are operational (barely) you have the upper bound config for a 12k user system at least right now ;-)