-
Bug
-
Resolution: Unresolved
-
Major
Job.getBuildHealthReports can be expensive, especially with Maven projects (see JENKINS-19392). Putting jobs into folders does not help, because Folder.getBuildHealthReports recursively traverses them, and the default WorstChildHealthMetric checks the result of each leaf. It should not be called synchronously during page rendering. Rather, WeatherColumn/column.jelly should use an AJAX callback of some kind, effective while the page is fronted. So you would get a quick page load, with some icons filling in progressively. Still puts load on the server but potentially much less.
- depends on
-
JENKINS-25081 Memory leak in ProgressiveRendering
- Resolved
- is duplicated by
-
JENKINS-20731 Dashboard rendering spends too much time in WeatherColumn
- Resolved
- is related to
-
JENKINS-19392 First-time display with many Maven jobs blocked in FingerprintAction.compact
- Resolved
-
JENKINS-18895 MavenModuleSetBuild.getResult is expensive
- Resolved
-
JENKINS-25073 Double-counting of health reports from child folders
- Resolved
-
JENKINS-25074 Build health computed twice per job
- Resolved
-
JENKINS-19828 Kill or rework auto refresh
- Closed
-
JENKINS-25078 Default health metric is potentially expensive
- Closed
-
JENKINS-36629 Use the run map to optimize calculating recent build health
- Closed
- relates to
-
JENKINS-18377 Improve the performance when listing many jobs (GSoC 2019, coding phase 2)
- In Progress