✳flâneur — a map of the web's best reading
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
Explore this link on the map →related reading
- NYSRGnotes.ekzhang.com
- How we got microVMs booting in under a seconddepot.dev
- Cloud Computing without Containers | The Cloudflare Blogblog.cloudflare.com
- What is AWS Lambda? - AWS Lambdadocs.aws.amazon.com
- Linux in a Pixel Shader - A RISC-V Emulator for VRChatblog.pimaker.at
- The best ways to save money on Lambda | theburningmonk.comtheburningmonk.com
- A blog about various stuff.: What I could not undiscover about Unikernels.fourlightyears.blogspot.com
- From bare metal to a 70B model: infrastructure set-up and scripts - Imbueimbue.com
- Oxide Computer Companyoxide.computer
- How we achieved truly serverless GPUsmodal.com
- Rethinking Serverless with FLAME · The Fly Blogfly.io
- How I helped fix sleep-wake hangs on Linux with AMD GPUs | nyanpasu64's blognyanpasu64.gitlab.io