降级构建系统的代价:以Kubernetes为例的案例研究
The Cost of Downgrading Build Systems: A Case Study of Kubernetes
AI总结:
本研究以Kubernetes等5个从Bazel降级到旧构建工具的项目为对象,分析降级前后的构建性能与资源消耗,发现降级虽可能提升可维护性,但会带来显著性能与成本代价,为大型项目构建工具选型提供权衡参考。
摘要:
由于开发者频繁调用构建系统,其性能会影响开发效率。现代基于制品的构建工具可加速构建,但已有研究表明,团队可能会放弃这类工具,转而使用更易维护的替代方案。尽管现有研究解释了降级的原因,但降级带来的影响仍未得到充分探索。\n本文针对Kubernetes项目开展案例研究,聚焦其从基于制品的构建工具Bazel降级为语言专属解决方案Go Build的过程。我们复现并分析了降级期间变更集的完整构建与增量构建情况。一方面,我们发现Bazel的构建速度比Go Build更快,完整构建耗时为23.06-38.66(单位未明确),最高可达75.19(单位未明确);但Bazel的内存占用比Go Build更大,分别为81.42-351.07(单位未明确)。在并行度设置方面,完整构建的并行度高于8时、增量构建的并行度高于1时,Bazel构建还会带来更高的CPU负载。我们估算,从Bazel降级最多可使CI资源成本增加76%(原文表述不完整,按现有内容翻译)。\n为探究观察结果是否具有普适性,我们在另外4个同样从Bazel降级到旧构建工具的项目上复现了Kubernetes相关研究。我们观察到,尽管构建时间的损失有所降低,但Bazel始终消耗更多内存。我们得出结论:放弃基于制品的构建工具,尽管在可维护性上有感知到的益处,但对于大型项目而言往往会带来可观的性能成本。我们的观察结果可帮助相关方在构建工具选型时权衡利弊。
英文摘要:
Since developers invoke the build system frequently, its performance can impact productivity. Modern artifact-based build tools accelerate builds, yet prior work shows that teams may abandon them for alternatives that are easier to maintain. While prior work shows why downgrades are performed, the implications of downgrades remain largely unexplored. In this paper, we describe a case study of the Kubernetes project, focusing on its downgrade from an artifact-based build tool (Bazel) to a language-specific solution (Go Build). We reproduce and analyze the full and incremental builds of change sets during the downgrade period. On the one hand, we find that Bazel builds are faster than Go Build, completing full builds in 23.06-38.66 up to 75.19 impose a larger memory footprint than Go Build of 81.42-351.07 respectively. Bazel builds also impose a greater CPU load at parallelism settings above eight for full builds and above one for incremental builds. We estimate that downgrading from Bazel can increase CI resource costs by up to 76 explore whether our observations generalize by replicating our Kubernetes study on four other projects that also downgraded from Bazel to older build tools. We observe that while build time penalties decrease, Bazel consistently consumes more memory. We conclude that abandoning artifact-based build tools, despite perceived maintainability benefits, tends to incur considerable performance costs for large projects. Our observations may help stakeholders to balance trade-offs in build tool adoption
机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。