将自动构建从 2-CPU 披萨盒重新调整为多 CPU 怪物？
我们当前的自动化构建由 1 个主盒和 4 个 core-2-duo 披萨盒（大约 2.5Ghz）组成，每个盒有 3 GB 内存，全部运行 Ubuntu Linux。 （使用 bamboo）
我被要求重新校准它以在一个或多个 Solaris 机器上运行。 我们当前的构建由 java 构建、长时间运行的集成测试构建和自动化 Selenium 测试的混合组成 - 一个相当典型的大型项目构建。 我们当前的环境有足够的容量，我们可能会失去一个核心左右而没有问题。
我们正在寻找具有“大”内存（16-32GB？我可以选择）的 8 CPU Solaris 机器。 或者也许是几台 4 CPU 机器？
我可以期望行为在单个框中以相当线性的方式扩展吗？ 我在这里寻找实际的经验； 关于如何进行的“理论”观察 IO可能会成为一个不太有趣的问题。
Our current automated build consists of 1 master box and 4 core-2-duo pizza boxed (at around 2.5Ghz), with 3 GB memory each, all running Ubuntu Linux. (Using bamboo)
I have been asked to recalibrate this for running on one or more Solaris boxes. Our current build consists of a mix of java builds, long running integration test builds and automated Selenium tests - a fairly typical large project build.
Our current environment has sufficient capacity, and we could probably lose a core or so without problem.
We are looking at 8 CPU Solaris machines with "large" amounts of memory (16-32GB? I can choose). Or maybe several 4 CPU machines ?
Can I expect behaviour to scale in a fairly linear manner within a single box? I am looking for actual experiences here; "theoretical" observations about how
IO may become a problem are not very interesting.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
事实上，我发现构建大部分时间都花在做某种 IO 上。 因此，增加 CPU 数量并没有您想象的那么有帮助。
但是，额外的计算机将具有额外的磁盘和网络带宽。 所以他们可能会提供更多帮助。 但是，您可以改进单个盒子的配置并可能获得相同的性能。
您通常同时运行多少个构建？ 如果您现在通常有 2 个构建在排队（并且 2 个正在运行），那么同时运行 4 个构建会是一种改进。 但除此之外并不会产生太大影响。
如今，配备 64 GB 内存的八核机器已成为新服务器的标准配置。 在此配置中，我建议使用 SSD 驱动器来改善磁盘访问时间并运行四到八个构建器/代理，如果您通常有八个或更少的构建等待，那么这可能就足够了。
Actually I find that builds spend most of their time doing IO of some sort. So increasing the number of CPUs doesn't help as much as you would think.
However, additional machines will have additional disks and network bandwidth. So they may help more. However, you can improve the configuration of a single box and possibly get the same performance.
How many builds you you typically have running at once? If you typically have 2 builds queued now (and 2 running) then having four builds running at once is an improvement. But more than that isn't going to make much difference.
Eight core machines with 64 GB of memory are surprisingly standard for a new server these days. In this configuration, I would suggest getting an SSD drive to improve disk access times and running four to eight builders/agents and that could be enough for if you typically have eight builds waiting at any time or less.
如果您的测试需要长时间运行，那么您可能会受益于两个构建，一个是运行所有快速测试的快速构建，另一个是可能仅在夜间运行的较慢的完整构建。
If your tests are long running, you may benefit from having two builds, a quick build which runs all the fast tests, and a slower full build which might be only run over night.