News for hackers. Stuff that matters.

A comment on We Replaced Firecracker with QEMU. Parent comment

Re:We Replaced Firecracker with QEMU by no_wizard on Monday July 10, 2023 @03:22PM (#36671594)
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.

[ Parent | on HN ]
Re:We Replaced Firecracker with QEMU by yokaze on Monday July 10, 2023 @04:22PM (#36672411)
Werner Vogels seems to disagree: https://twitter.com/Werner/status/25137574680
[ Parent | on HN ]
Re:We Replaced Firecracker with QEMU by rob-olmos on Monday July 10, 2023 @06:03PM (#36673606)
Tweeted Sep 21, 2010, might still be true for EC2 VMs though.
[ Parent | on HN ]
Re:We Replaced Firecracker with QEMU by cthalupa on Monday July 10, 2023 @07:02PM (#36674197)
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.
[ Parent | on HN ]