I noticed pages were taking a bit longer than expected to load, so I ended up upgrading to a new server. It already seems faster (and let’s hope it stays that way too). As always, let me know if you notice any peculiarities that might have been caused by the upgrade.
I’m not an admin, so I’m not qualified to answer that part, but I also came from kbin.social originally. I moved to fedia.io/Mbin when kbin.social and kbin itself died. I’ve definitely had a much better time on Fedia/Mbin as far as stability. I think that probably comes down to several factors:
- the stability of the software itself
- an attentive admin who’s around to kick the tires
- less load on the server/s
For comparison, here’s the last successful capture archive.org made of the kbin.social stats page. It lists 64601 users and 115388 threads. Here’s the present-day fedia.io stats page which as I write this comment is reporting 5132 users and 9629 threads. Naively extrapolating from these figures, kbin.social was apparently taking >10 times the load that the largest Mbin server is currently. On the one hand, it would be nice to see Mbin grow to the heights of early kbin, but the current situation is far more manageable for these mostly out of pocket/donation-supported projects.
I try to help and closely work together with @jerry@infosec.exchange (who is the admin of that instance) a lot to get Mbin as stable as possible. So to glad to hear you notice the end result.
@melroy @jwr1 @arotrios @vaguerant I cannot express how awesome the mbin team has been. I have no idea how kbin.social was able to operate with that many users while running kbin. I can definitely see mbin working for that large of a user base, though.
I have no idea how kbin.social was able to operate with that many users while running kbin.
Where was some custom things doing on for sure. Maybe @piotrsikora@pol.social can recall how they get kbin running at all back in the days with that many users.
