zlacker

>>hugodu+(OP)
The article did an ok job of explaining the firecracker limitations they ran into but it was extremely skimpy when it came to qemu and just rushed to the conclusion “we did a lot of work so try our product.”

>>Comput+fh
yeah I was reading so I could find out what they did.

I understand that they need to sell their product but jeez. don't leave us hanging like that

>>naikro+Mh
I didn't want to go into all the technical details, but we have another write-up that goes into details about RAM management: https://github.com/hocus-dev/hocus/blob/main/rfd/0003-worksp...

Other than making sure we release unused memory to the host, we didn't customize QEMU that much. Although we do have a cool layered storage solution - basically a faster alternative to QCOW2 that's also VMM independent. It's called overlaybd, and was created and implemented in Alibaba. That will probably be another blog post. https://github.com/containerd/overlaybd

>>hugodu+Ep
> I didn't want to go into all the technical details

HN is here for the technical details ;)

>>Comput+yv
that should be the HN motto!

>>gunapo+lz
Thirded.. Ed.