4 ms·
Thanks! We will post detailed technical docs on design/features soon. FC improved kernel boot up time (by stripping unnecessary functionality). However, runtime
by ashishbijlani 5y ago
Thanks! We will post detailed technical docs on design/features soon. FC improved kernel boot up time (by stripping unnecessary functionality). However, runtime performance takes a hit due to I/O virtualization/emulation: https://www.usenix.org/system/files/nsdi20-paper-agache.pdf https://www.usenix.org/system/files/nsdi20-paper-agache.pdf
- tptacek 5y agoHave you measured the performance difference between your system and Firecracker? I'm interested in knowing more about how you're quantifying this. As I said, it'd be easier to engage with this if your technical overview was public. It's also a little tricky to get my head around how you're simultaneously winning on I/O performance by not virtualizing it, and also shielding me from host kernel vulnerabilities. Some of that I/O overhead you're talking about is spent in the service of putting a security boundary between my guests and my host.
- ashishbijlani 5y agoYes, we will post the numbers soon. However, what I was alluding to in my last comment was that FC runtime performance is far from native (i.e., no VMs). Therefore, there's definitely room for improvement. Depending on the use case, that may or may not be meaningful.
- tptacek 5y agoLooking forward to seeing more about this. Thanks!