Why We Replaced Firecracker with QEMU | Hocus Blog
At CodeSandbox we use Firecracker for hosting development environments, and I agree with the points. Though I don't think that means you should not use Firecracker for running long-lived workloads.
We reclaim memory with a memory balloon device, for the disk trimming we discard (& compress) the disk, and for i/o speed we use io_uring (which we o... See more
We reclaim memory with a memory balloon device, for the disk trimming we discard (& compress) the disk, and for i/o speed we use io_uring (which we o... See more
Article
Still haven't found the original story but here is one https://blog.codinghorror.com/new-programming-jargon/... See more
