Details
-
Type:
Improvement
-
Status: Resolved (View Workflow)
-
Priority:
Critical
-
Resolution: Incomplete
-
Component/s: other
-
Labels:None
-
Environment:Platform: All, OS: All
-
Similar Issues:
Description
We're running quite an extensive setup with dozens of projects and thousands of
builds for each project. At the moment we're purging build artefacts but keep
the actual build history+metadata indefinitely. Maybe because of that, startup
up hudson now takes in excess of 40 minutes. vmstat shows the disk being busy.
It would be preferable if startup time of hudson were unaffected by the number
of builds or projects. I'm putting this as "enhancement", but it's really a
rather important one for us.
Attachments
Issue Links
- depends on
-
-
- Closed
-
- is duplicated by
-
JENKINS-3523 Hudson with about 150 defined jobs uses 40 min on boot time
-
- Closed
-
-
-
- Closed
-
- is related to
-
-
- Resolved
-
-
-
- Resolved
-
Activity
This issue is too vague and general to be worth keeping open. If there are specific startup performance problems reproducible in current versions of Jenkins they should be filed with details.
Relevant information for filing performance-related issues can be found here:
https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue
https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump
@huybrechts, http://n4.nabble.com/Restart-hudson-takes-too-much-time-td386719.html is dead.
@Jesse this is pretty specific. Create "dozens of projects and thousands of builds" (as per the issue description) and then start Jenkins.
Large numbers of projects and builds slowing down Jenkins startup has been corroborated by many people on this issue.
Are you not able to reproduce this issue?
What details do you lack?
has been corroborated by many people on this issue.
It's less clear if you consider that Jenkins implemented lazy loading of build records from Oct 2012 to some time in early/mid 2013 (until the major issues were worked out).
Then there's the case that some plugins have a tendency to require loading all build records, which defeats this optimization.
What details do you lack?
Stack traces would be helpful. Lists of installed plugins. Maybe even Support Core plugin support bundles. And of course everything with recent Jenkins versions only.
And even then, at least my expectation is that many different causes contribute to a long startup time, which will need to be fixed one by one rather than gathered in a catch-all issue.
@francisdb
> If all builds ever executed need to be read in before jenkins kan show it's main ui this indeed sounds like a design issue
This issue has been already solved in 1.485 (
JENKINS-8754). However, there were many regression issues caused by the lazy loading, hence it is recommended to use 1.532+Now Jenkins loads only the required set if builds. Some plugins may require all builds to be loaded, but it is a topic for additional issues on Jenkins JIRA.