缓慢的 Buckminster 插件解析
我正在使用 ant 运行无头 Buckminster 构建，由于某种原因，需要 4 个多小时才能完成所有需要构建的插件的解析。大约有 350 个插件需要构建，所有这些插件都已经在本地文件系统上，并在 rmap 文件中作为“本地”提供程序提供。
我尝试提高日志记录级别来调试，看看构建在 4 小时内忙于做什么，但前 30 秒左右只有日志语句，然后日志记录停止，CPU 使用率上升到大约 100%，直到解决大约4小时后终于完成。
对于这个缓慢的过程，有人有任何进一步的调试技巧或可能的解决方案吗？
I am running a headless Buckminster build using ant that for some reason is taking 4+ hours to finish resolving all the plugins that need to be built. There are about 350 plugins that need to be built, all of which are already on the local filesystem and are provided in a rmap file as "local" providers.
I have tried increasing the logging level to debug see what the build is busy doing for 4 hours but there is only log statements for the first 30 seconds or so, then the logging stops and the cpu usage goes up to about 100% until the resolution finally finishes after about 4 hours.
Does anyone have any further debugging tips or possible solutions to this slow process?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
尝试转储线程堆栈来跟踪哪个组件正在工作并且会消耗大量资源。
Trying to dump the thread stack to trace which component is working and cost much resource.
更新到最新版本的 Buckminster 解决了这个问题。添加了一些工件解析缓存，大大减少了 Buckminster 解决传递依赖项所花费的时间。
Updating to the latest version of Buckminster resolved this. Some artifact resolution caching was added that greatly decreased the amount of time Buckminster spent resolving transitive dependencies.