Why We Replaced Firecracker with QEMU | Hocus Blog
hocus.dev · 894 words · saved by 1 readers
Firecracker is not the best choice for all kinds of workloads.
Firecracker, the microVM hypervisor, is renowned for being lightweight, fast, and secure. It's excellent for running short-lived workloads, which is why it's the backbone of AWS Lambda. Our initial prototype for Hocus, a self-hosted alternative to Gitpod and GitHub Codespaces, utilized Firecracker. However, after weeks of testing, we decided to entirely replace it with QEMU. A little-known fact about Firecracker is its lack of support for many modern hypervisor features, such as dynamic RAM management, which is vital for long-lived workloads. In this post, I will explain why Firecracker might
saved by
related reading
- firecracker/docs/design.md at main · firecracker-microvm/firecrackergithub.com
- GitHub - JustVugg/colibri: Run frontier MoE models on hardware you already own — pure C, zero deps, experts streamed from disk. Tiny engine, immense model. 🐦github.com
- How to Rack 30 Petabytes of Storage | blogsi.inc
- nsdi20-paper-agache.pdfusenix.org
- On-demand Container Loading in AWS Lambdaarxiv.org
- How we got microVMs booting in under a seconddepot.dev
- Rethinking Serverless with FLAME · The Fly Blogfly.io
- Cloud Computing without Containers | The Cloudflare Blogblog.cloudflare.com
- All my favorite tracing tools: eBPF, QEMU, Perfetto, new ones I built and more - Tristan Humethume.ca
- I was wrong! zswap IS better than zramlinuxblog.io
- Hono v4.0 | Hacker Newsnews.ycombinator.com
- Can I run AI locally? | Hacker Newsnews.ycombinator.com