詹金斯(Jenkins)初次访问时非常慢 [英] Jenkins is very slow on first visit
问题描述
詹金斯在清晨第一次造访时非常慢.如果我们重新启动Jenkins服务器，也会发生这种情况.
Jenkins is very slow on the first visit in the early morning. This also happens if we restart the Jenkins server.
因此，第一个访问jenkins的开发人员有时需要等待3分钟. 我们认为这是构建负载的问题.因此，我们将所有构建工作移至詹金斯奴隶.但是问题尚未解决.
So the first developer accessing the jenkins has sometimes wait up to 3 minutes. We thought it was an issue with the build load. So we moved all build-jobs to a jenkins slave. But the issue has not been solved with it.
由于重新启动后性能似乎总是很差.我认为詹金斯将很多东西读到内存中. 我们如何执行jenkins来预缓存内容?如果需要，我们可以给詹金斯大量的RAM.希望缓存可以解决速度问题.
Since the performance seems to be always bad after restart. I assume jenkins reads a lot of stuff into memory. How can we enforce jenkins to precache stuff? We can give jenkins a hughe amount of RAM if needed. Hopefully the cache will solve the speed issues.
推荐答案
很难确切地说出是什么原因导致您的Jenkins实例启动需要很长时间才能启动，尽管您安装的插件之一很可能是罪犯.
It would be difficult to definitively say what is causing your Jenkins instance to take so long to startup, though it is highly likely that one of your installed plugins is the offender.
例如:
- JENKINS-17837 -下游构建视图插件
- JENKINS-24945 -全局构建统计信息插件
- JENKINS-17837 - Downstream Build View Plugin
- JENKINS-24945 - Global Build Stats Plugin
当然，除了这两个插件外，还有其他一些插件具有错误/问题，导致启动时间也很慢.有些可能有问题，后续版本已解决了性能问题.
Surely there are other plugins besides these two which have bugs/issues resulting in slow startup times as well. Some may have had issues and subsequent versions have addressed the performance issues.
因此，如果不能完全解决问题，请执行以下步骤至少应查明罪魁祸首:
Therefore, performing the following steps should at least reveal the culprit if not entirely fix the issue:
- 将Jenkins升级到最新的稳定版本
- 将所有插件升级到其最新的稳定版本
- 重新启动詹金斯
- 如果启动仍然缓慢，请一次删除一个插件(确保在必要时保存各自的配置)
如果升级到最新版本并不能缩短启动时间，则步骤4应该可以找出问题的根源.
If upgrading to the latest versions does not improve your startup time, step 4 should reveal the culprit.
这篇关于詹金斯(Jenkins)初次访问时非常慢的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
