I think their usecase makes a lot of sense as their workloads consume a predefined amount of ram. As a customer you rent a VM with a specified amount of memory so fly.io does not care about reclaiming it from a running VM.
This is why paying for dedicated memory is often more expensive than its counter part, because that dedicated memory is not considered as part of pooling.
E.g. using the firecracker jailer: https://github.com/firecracker-microvm/firecracker/blob/main...
Just because you can doesn't mean you should.
Malloc will happily “return” the 15 TiB you asked for.
If 10000 people called 911 at the same time, only a tiny fraction would get through (and even fewer would get help).
Evacuating a large city by road would result in giant traffic jams.
There are 5-8x as many parking spots as there are cars (and we still can’t find a goddamn spot).
And of course… the great toilet paper shortage of 2020.
Fly.io themselves admitted they’re oversubscribed and AWS is doing the same for years now
The entire vibe of this thread is
1) everyone is doing it
2) efficiency drives cost down (to the vendor) but those savings are not passed to the consumer
3) "hardware you pay for when you need it", all predicated on the at IF and it doesn't happen.
Oversubscription should always be opt-in, otherwise it is an underhanded scam.
And then they learn all hotels are doing exactly same thing. One hotel doing is risk, all hotels doing is industry standard.
Airlines, hotels, restaurants, doctors and so on oversubscribe all the time. Whoever complains are free to move and add to their further disappointments.
Chances are you are using systems that do this and you haven't even noticed.