3 ms·
AWS, Rackspace et al. use hypervisors already, so we're trending toward 4 layers: hypervisor -> monolithic kernel -> containers -> application Unikernels co
by m0th87 12y ago
AWS, Rackspace et al. use hypervisors already, so we're trending toward 4 layers:
hypervisor -> monolithic kernel -> containers -> application
Unikernels collapse it to:
hypervisor -> unikernel/application
It's certainly more elegant, although I'm skeptical of the purported performance gains as well, simply because so many optimizations have been thrown into traditional kernels.
- jdf 12y agoIf you are using a more minimal hypervisor (see my other comment on the parent), then there do seem to be some measurable gains. I've seen a few papers in this style: https://www.usenix.org/conference/osdi14/technical-sessions/presentation/peter https://www.usenix.org/conference/osdi14/technical-sessions/... We describe the hardware and software changes needed to take advantage of this new abstraction, and we illustrate its power by showing improvements of 2-5 in latency and 9 in throughput for a popular persistent NoSQL store relative to a well-tuned Linux implementation. That said, a simple application like memcached might be currently latency-bound by the kernel's network stack, but a more complex application that reads from disk (even SSD) won't be.