buildHealth.jelly asks for both job.buildHealth and job.buildHealthReports, causing Job/Folder.getBuildHealthReports to be called twice just to render a single table cell. I would guess that the performance problem comes in the first call, and the second call is mostly working off a hot cache, but if you are under memory pressure it is always possible that garbage collection has to run between the two calls and so work is wasted. I see no need to call job.buildHealth; should suffice to assume that the implementation is simply going to be to look up the first element in job.buildHealthReports (as it is in both Job and Folder).

          [JENKINS-25074] Build health computed twice per job

          Jesse Glick created issue -
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-25075 [ JENKINS-25075 ]
          Jesse Glick made changes -
          Assignee New: Jesse Glick [ jglick ]
          Jesse Glick made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          Jesse Glick made changes -
          Labels Original: health performance view New: health lts-candidate performance view
          Oliver Gondža made changes -
          Labels Original: health lts-candidate performance view New: 1.580.3-fixed health performance view
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 158975 ] New: JNJira + In-Review [ 195954 ]

            jglick Jesse Glick
            jglick Jesse Glick
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: