Containers are interesting and the technology is emerging, but for 1-2% overhead it just isn't as critical as its often held.
Containers are interesting and the technology is emerging, but for 1-2% overhead it just isn't as critical as its often held.
https://major.io/2014/06/22/performance-benchmarks-kvm-vs-xe...
-but with de-duplication of a solution like vmware, approaches 0.
Containerization seems like a massive win when you're trying to fit a bunch of stuff in a single Digital Ocean VM, etc. When you're running many machines in a data center, though, it becomes dramatically less valuable.
You're right that once you've hit rack levels of virtualization, you've already hit the management overhead requirements to use VMs.
In my mind, it isn't about processing or IO overhead. It's about the overhead for management. It's a trade-off. Some applications are better managed as whole systems (VMs), whereas others are more building block-ish and probably better as containers. The two technologies are pretty complimentary.
[1]: https://www.freebsd.org/cgi/man.cgi?query=capsicum&sektion=4
For CPU and RAM, but the overhead for I/O is much higher.
technologies like deduplication of storage and memory can paradoxically improve performance over bare metal
In principle there's no reason why containers can't use those same technologies, although AFAIK currently Linux can't do memory dedupe for containers.
Hardware virtualized I/O is a thing now as well, and in that case as well the overhead has shrunk to marginal. Add external storage (iSCSI), and things get much more complex.
Much of the argument about virtualization is about ten years+ old. It once represented a significant additional overhead, but that simply isn't true at all now.