知识卡片
边车数量放大资源成本
每个服务实例配一个代理,会把单个代理的内存和 CPU 开销乘以实例数;规模增长还增加升级与运维成本。选择边车网格时,应按实例、节点和实际配置测算总资源,而不是只引用单个代理的轻量指标。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- · 查看原书依据
Many of today’s popular service mesh solutions require you to add and run a proxy sidecar container, such as Envoy, Linkerd-proxy, or NGINX, to every service or application running within your cluster. Even in a relatively small environment with, say, 20 services, each running five pods spread across three nodes, you will have 100 proxy containers running. However small and efficient the proxy implementation is, the sheer duplication of the proxies will impact resources.
参考来源
- 位置:《Mastering API Architecture》第4章《Service Mesh: Service-to-Service Traffic Management》之《The Cost of Running Sidecars at Scale》(源文件:_epub-src/OEBPS/ch04.xhtml)
- 结论依据:原文以20服务各5实例说明会运行100个代理,指出代理复制带来资源开销,并举配置影响内存的案例。
- 原始内容:Many of today’s popular service mesh solutions require you to add and run a proxy sidecar container, such as Envoy, Linkerd-proxy, or NGINX, to every service or application running within your cluster. Even in a relatively small environment with, say, 20 services, each running five pods spread across three nodes, you will have 100 proxy containers running. However small and efficient the proxy implementation is, the sheer duplication of the proxies will impact resources.