3 ms·
I'm curious about restarts and snapshotting: would it be feasible to reset a microVM for each incoming request?
by detaro 7y ago
I'm curious about restarts and snapshotting: would it be feasible to reset a microVM for each incoming request?
- mrkurt 7y agoSnapshot / suspend isn't doable yet, but it sure would be nice. We've booted some apps in Firecracker in <20ms, so if you build the app properly you can absolutely do a new VM per request or TCP connection even.
- scarface74 7y agoYeah, this is what AWS does....
- ec109685 7y agoNo it doesn't. It pre-inits the Firecracker VM's before the first request: https://www.usenix.org/system/files/nsdi20-paper-agache.pdf https://www.usenix.org/system/files/nsdi20-paper-agache.pdf
- scarface74 7y agoI meant the part about one request per VM.
- whalesalad 7y agoMight consider a pre-emptive approach that always keeps a few warmed up and ready to receive a request. The determination on how many to keep warm could be a function of traffic over the last X period of time.
- hinkley 7y agoWasn't fastcgi essentially about starting new processes ahead of time and then doling them out as new requests came in? Worked quite well for bursty traffic, and for sustained traffic was about the same. Feels like a similar strategy could be apropos here. And if I'd read farther down the chain, someone said that Amazon already does this.