/kbin server update - or how the server didn't blow up

Currently, on the main instance, people have created 40191 accounts (+214 marked as deleted). I don't know how many are active because I don't monitor it, but once again, I greet all of you here :) In recent days, the traffic on the website has been overwhelming. It's definitely too much for the basic docker-compose setup, primarily designed for development use. I was aware of the possible consequences of the situation happening on Reddit, but I assumed that most people would migrate to one of the Lemmy instances, which already has an established position. I hoped that a few stray enthusiasts would find their way to kbin ;)

The first step was to upscale the VPS to a higher version (66.91EUR). It quickly turned out that it wasn't enough. I had to enable CF protection just to keep the website responsive, but the response times were still very slow. At this stage, the instance was practically unusable. The next step was a full migration to a dedicated server (100EUR, the current hardware). It can be done relatively quickly, so it resulted in a 5-minute technical break. Despite the much higher parameters, it didn't get any better. It became clear that the problem didn't lie there. I'm really frustrated when it comes to server administration. That was the moment when I started looking for help. Or rather, it found me.

A couple days ago I wrote about how kbin qualified for the Fast Forward program. To be honest, I did it out of pure curiosity and completely forgot because a lot was happening during that time. During the biggest fire incident, Hannah ( @haubles ) reached out with a proposal to help. I outlined the situation (in short: the server is dying, I don't even know what I need, help! ;). She quickly connected us with Vlad ( @vvuksan ) and Renaud ( @renchap ). I was probably too tired because I don't know if the whole operation lasted 60 minutes or 6 hours, but after a series of precise questions and getting an understanding of the situation, the guys themselves adjusted the entire job. I love working with experts, and it's not often that you come across individuals so well-versed in the fediverse. Thanks to Hannah's kindness, we will be staying there a bit longer. Currently, fastly.com handles the caching layer and processes images. Hence those cool moving thumbnails ;)

Things were going well at that point. I could disable Cloudflare protection. Probably thanks to that, many of you are here today, and we got to know each other a bit better :) However, even then, when I tried to enable federation, the server would stop working.

Around the same time, Piotr ( @piotrsikora ), whom I already knew from the Polish fediverse, contacted me. He is the administrator of the Polish Mastodon instance pol.social, operates within the ftdl.pl foundation, and specializes in administering applications with a very similar tech stack. I made the decision to grant him server access. It only took him a few moments, and he came back to me with a few tips that allowed us to enable federation. In the following days, there was more of it, and we managed to reach the current level. I think it's not too bad.

Nevertheless, managing the instance has taken up about 60% or more of my time so far, which prevents me from fully focusing on current tasks. That's why I would like to collaborate with Piotr and hand over full care of the server to him. Piotr will also take care of the security side. Now I have to take this much more seriously. We still need to work out the terms of cooperation, but I want you to know the direction I intend to pursue.

We also need to migrate to a new environment because one server will sooner or later become insufficient. This time, I want to be prepared for it. This may be associated with transient issues with the website in the coming days.

The next two updates will still be about project funding (I still can't believe what happened) and moderation. The following ones will be more technical, with descriptions of changes and what contributors are doing on Codeberg. I would like to be here more often, but not as an admin, just as myself.

Thank you all for this.

P.S. In private messages, I also received numerous offers of help that I didn't even have a chance to read and respond to. You are the best!

chillicampari,
chillicampari avatar

@ernest this was an extraordinary situation with several crisis points on a platform in early development (as far as mass usage is concerned) and you were able to keep a cool head, keep things going and also keep people informed of the situations as they were developing. I am happy to read that you have help now (and it looks like really great expert help) and that you can take a break/retirement from admin and enjoy it with the rest of us. Bravo!

st3ph3n,
st3ph3n avatar

Your work is appreciated, @ernest !

thesanewriter,

You're doing great @earnest, I may be on Lemmy but kbin.social has become a great community and is dominating my federated feed, which tells me other people agree

catarina,
catarina avatar

Looking forward to the follow-up posts with technical details, if you do find the time to write them up ofc! As a new kbin user, my thanks for all the hard work and for welcoming us here <3

Juliie, (edited )

It would be really helpful to have a website listing servers which are flooded and which are encouraging new members. And yeah the uptime too.

VulcanSphere,
VulcanSphere avatar

Great update!

Keep up the good work.

babelspace,
babelspace avatar

I had a feeling that the silence over the last few days was a sign that a huge amount of work was happening behind the scenes. I also think you’re doing an excellent job of communicating with us. Thank you for all your effort that’s allowed this community to grow.

Pilirin,

@ernest your achievements with this piece of software is going to go down in internet history, i hope you know that. you have already written your name into the history books. you deserve congratulations and very sincere thanks.

adonis,
adonis avatar

@ernest Regarding servers... did you have a look at Hetzner's server auctions. They tend to have 8c/16t servers for 40-50 bucks.

Also, I've seen kbin uses PHP at it's core. Do you consider switching to a golang stack, which is known to be more resource-friendly than PHP.

Badabinski,

Methinks that a rewrite from PHP to Go would be a pretty massive undertaking. PHP's performance characteristics have gotten a lot better as the language and various runtimes have improved, although it's not anything like Go. I think the best route would be for someone to implement another federated link aggregation system in Go, so then we'd have a diverse selection to choose from — Lemmy in Rust, kbin in PHP, this hypothetical new platform in Go, along with everything else out there. A heterogeneous system is good for the continued health of the threadiverse IMO.

stevecrox,
stevecrox avatar

That isn't the issue.

A complete rewrite of the application might add capacity, but its vertical, you stack increase load in one instance. No matter how much performance you extract eventually you run out of capacity.

As scales increase you need to add horizontal capacity. This is the idea of adding 2, 10, 100 servers. That means breaking out services into stateless parts which can run concurrently (or managed state behaviour).

This is where something like Kubernetes comes into play, since its designed to manage docker images over hubdreds of servers. Instead of using every last bit of capacity from one server you spread it.

Similarly postgres like most SQL platforms doesn't particularly scale beyond 1 instance.

Facebook invented Apache Cassandra for this reason, it was the first NoSQL database and is designed to deploy in multiples of its replicaset number (3 is the default).

Having data spread over 3, 30, 300 is less efficient, but you know have 3,30, 300 servers responding.

The other advantage is horizontal scaling is fault tolerant by design.

There is an argument for compiled languages like Go, C# and Java, but honestly the next big win is making as much as possible scale horizontally.

djwu,

Thank you for the update

BBKuma,
BBKuma avatar

Thanks for the hard work ernest!! I'm glad you were able to find some help and take some workload off you.

NotAPenguin,

Thank you everyone!

eric,

thanks for proving the community this - really enjoying this place <3

BraveSirZaphod,
BraveSirZaphod avatar

I'd been doing a little shopping around over the past few weeks as I've been getting ready to properly leave my 11 year old (cringe) Reddit account behind. Lemmy does seem promising as well, but I do have some concerns about the developers, and while of course no one is perfect, as it's still the early days, I'd much prefer to throw my support behind people to whom I can do so guilt-free. So far at least, this has felt right up my alley, and while I am trying to use this moment to cut down a bit on my internet time in general, I'm definitely happy to be here!

asjmcguire,
asjmcguire avatar

The biggest reason I'm here, is Ernest. Getting in when a project is just getting off the ground, let's users have some say about the direction of things and features. And Ernest is very responsive to the community and asking for feedback. That's exciting, and makes the whole thing feel more of a community.

stinkypoopsalot,

I'm glad you are here. Thank you for your work.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • kbinMeta
  • DreamBathrooms
  • magazineikmin
  • thenastyranch
  • Youngstown
  • mdbf
  • rosin
  • slotface
  • InstantRegret
  • khanakhh
  • Durango
  • kavyap
  • osvaldo12
  • tacticalgear
  • GTA5RPClips
  • megavids
  • ngwrru68w68
  • everett
  • tester
  • ethstaker
  • cisconetworking
  • cubers
  • modclub
  • provamag3
  • anitta
  • normalnudes
  • Leos
  • JUstTest
  • lostlight
  • All magazines