Ideas to help keep the server up on patch day

[dafluf]

Over the last 2 patches, I couldn't help but notice that there is some trouble managing the large load on your server, as soon as the patch is released. That's why I've got a few ideas, which might be able to help you keep the servers up

1. Peer 2 peer

It might, or might not be feasible for you to implement peer 2 peer technologies in your patcher. If you do, make sure it's transparent (as in, you clearly let people know you're using their network connection for this purpose), and provide the option to turn it off. Why should you let people turn it off? Because, there are some countries (like mine), where a lot of ISP's put a limit on how much data you may upload each month. It's not fun to find out you have been kicked to small band because a certain game decided to drain your upload while patching.

2. A queue system

A queue system definitely seems like a good idea. This way, when your server has reached capacity, you at least give feedback to the users about what is going on. It also allows the user to keep the patcher running while they do something else, instead of having to try and connect every now and again. It also allows you to keep some system resources at hand to keep your forum and website going.

It certainly would mean the situation is handled gracefully.

3. A server upgrade

The most obvious solution is of course a server upgrade. It is certainly a viable solution. The only constraint on it, is how much money you can/want to spend on an upgrade, which will only be used on patch days.

4. Steam

It's also possible to use steam. This way, you let an external company worry about deploying the game. I'm not sure what the conditions are for that service though. And some users might not like using steam.

Those are the ideas I could come up with.

The download doesn't need to be super smooth, or super fast (Everything is still in alpha after all). But overloading the server, which also needs to handle your website and forum, doesn't seem like a very good idea.

[tomato3017]

Easy to do if the servers are setup in the correct manner. Use Amazon Ec2 or alternate with a load balancer. Have it setup to automatically launch new EC2 instances on a high load and bam, instant capacity.

[Neomatt]

Easy to do if the servers are setup in the correct manner. Use Amazon Ec2 or alternate with a load balancer. Have it setup to automatically launch new EC2 instances on a high load and bam, instant capacity.

At a high price... Given the number of users and the size of the software, it's TBs of data, and Amazon is charging about 120$ for 1 TB, so it can go to 1000$ for a single patch. Pretty sure they don't have that lying around for each version.

About dafluf's ideas, I'll add "another unique server for downloads only". That would at least leave the forum/store available (but about 100 threads "DOESNT WORK UGH" would be created on patch day)

Steam is the best of the bunch for me (externalized, allows for diffs/patches, and I already run it via Steam), but yeah, some people don't like it, and I can understand why.

Also, they need to get their cut and current users need to get Steam keys, so that's not as easy/fast as the others.

[sal_vager]

Yeah dafluf, this stuff has been thought of by now

(1) Not going to happen, don't bother to ask or suggest this one.

(2) Might help, but the patcher was just not ready, N3X15 was not given the time he needed.

(3) Costly, and currently too expensive for the few days a year that Squad need it, perhaps renting a server for a few days would be an idea though.

(4) Will happen, but only when KSP reaches 1.0

This does not really belong in Suggestions though, so I'm moving it to Off-Topic