知识卡片
容器隔离需计入资源竞争
容器将代码及依赖打包为部署单元,提升环境一致性与交付灵活性;它仍共享宿主资源与内核,存在资源竞争和抽象层开销。性能敏感服务应实测。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
原书出处
参考来源
- 位置:《Principles of Software Architecture Modernization》第8章《Embracing New Technology》(源文件:`_epub-src/OPS/ch08.xhtml`,归一化正文 [33620:37873))
- 结论依据:原文比较容器好处与 CPU、内存、磁盘和内核共享的代价。
- 原始内容:Containers have cons as well; any time you introduce another abstraction layer, you increase complexity, and potentially impact performance, overhead and throughput. Some examples: IBM has an interesting paper comparing the performance of virtual machines and containers: https://dominoweb.draco.res.ibm.com/reports/rc25482.pdf Uber reported 5-10% overhead by running Cassandra on Containers http://highscalability.com/blog/2016/9/28/how-uber-manages-a-million-writes-per-second-using-mesos-and.html Isolated containers compete for CPU, memory, disk, and kernel resources, which means there is some risk of resource contention.