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
-
JENKINS-8754 ROADMAP: Improve Start-up Time
-
- Closed
-
- is duplicated by
-
JENKINS-3523 Hudson with about 150 defined jobs uses 40 min on boot time
-
- Closed
-
-
JENKINS-2890 very low performance when starting the server
-
- Closed
-
- is related to
-
JENKINS-20046 Massive Jenkins slowdown when jobs in Queue (due to Queue.maintain())
-
- Resolved
-
-
JENKINS-25473 Unnecessarily slow & serialized I/O for top-level item loading in loadTasks
-
- Resolved
-
@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.