zlacker

>>hugodu+(OP)
Fly uses Firecracker, and they host long-running processes. I wonder what's their opinion about it.

>>wiradi+l2
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.

>>gorbak+U4
Depends on if they're using smart memory allocation to keep costs lower, IE, if they can pattern that certain workloads only need N amount of memory at Y time, they can effectively borrow memory from one VM for usage in another that has an opposite statistical likelihood of needing that memory.

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.

>>no_wiz+Pa
Shit like this is how you burn customers and then they find out you aren't changing the sheets, they change hotels.

Just because you can doesn't mean you should.

>>nerpde+hA
It’s a common technique though. I believe it’s called oversubscription, where you rent the same hardware to more tenants hoping they won’t use it all at once.

Fly.io themselves admitted they’re oversubscribed and AWS is doing the same for years now

Source: https://fly.io/blog/the-serverless-server/

>>ushako+aT
We're not using virtio memory ballooning right now (we've never had the time to get it working).