
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 only... 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 only... See more
Article
In building Sublime, I've found myself getting distracted by shiny feature syndrome so much that I realized it'd be helpful to explicitly lay out what actual problems I was trying to solve for myself.
r/PKMS - Reddit
At the beginning I said I didn't think the Alto Architecture is better than current approaches. The main reasons are the things that Alto did not have:
As a consequence of the... See more
- No virtual memory or any memory protection
- No executive mode, to support a trusted operating system or contain untrusted code
- No virtualization capability
- No parallelism
- No caches
As a consequence of the... See more