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
Super common though. Everyone from Hetzner to AWS does this, unless you specifically pay for full allocation, which is typically ~2x the price.

Chances are you are using systems that do this and you haven't even noticed.

>>no_wiz+Cf1
Werner Vogels seems to disagree: https://twitter.com/Werner/status/25137574680

>>yokaze+Ns1
Tweeted Sep 21, 2010, might still be true for EC2 VMs though.

>>rob-ol+4M1
There's the 't' series of instances that offer burstable CPU. AFAIK still 1:1 on memory though, and there's models that allow you to pay to stay un-throttled when using t family instances vs. getting throttled when out of burst credits.