[JENKINS-48350] Cache estimated duration for execution

        Alexander A created issue -

        Oleg Nenashev added a comment -

        It has been released in 2.92.
        jimilian in order to mark is as LTS candidate, the changelog on jenkins.io needs to be updated

        Oleg Nenashev added a comment - It has been released in 2.92. jimilian in order to mark is as LTS candidate, the changelog on jenkins.io needs to be updated
        Oleg Nenashev made changes -
        Resolution New: Fixed [ 1 ]
        Status Original: Open [ 1 ] New: Resolved [ 5 ]
        Oleg Nenashev made changes -
        Labels Original: performance New: lts-candidate performance
        Oliver Gondža made changes -
        Labels Original: lts-candidate performance New: 2.89.3-rejected lts-candidate performance
        Oleg Nenashev made changes -
        Link New: This issue is related to JENKINS-48821 [ JENKINS-48821 ]
        Oliver Gondža made changes -
        Labels Original: 2.89.3-rejected lts-candidate performance New: 2.89.3-rejected 2.89.4-fixed performance

        Code changed in jenkins
        User: Alexander Akbashev
        Path:
        core/src/main/java/hudson/model/Executor.java
        http://jenkins-ci.org/commit/jenkins/e0ea7a648ed6970897ea2c49bc662439ec4e4110
        Log:
        JENKINS-48350 Cache estimated duration for execution

        In case of having 1000s of ongoing builds opening main pages can take
        some time if list of executors are opened. It happens because for every
        queury that comes from jelly we re-calculate the value from scratch. And
        calculation needs to load some builds from disk. The worst thing is that it
        happens for every user separately.

        (cherry picked from commit d7b120fea37b46b863c89acb638d04cdddc868b4)

        SCM/JIRA link daemon added a comment - Code changed in jenkins User: Alexander Akbashev Path: core/src/main/java/hudson/model/Executor.java http://jenkins-ci.org/commit/jenkins/e0ea7a648ed6970897ea2c49bc662439ec4e4110 Log: JENKINS-48350 Cache estimated duration for execution In case of having 1000s of ongoing builds opening main pages can take some time if list of executors are opened. It happens because for every queury that comes from jelly we re-calculate the value from scratch. And calculation needs to load some builds from disk. The worst thing is that it happens for every user separately. (cherry picked from commit d7b120fea37b46b863c89acb638d04cdddc868b4)
        Jesse Glick made changes -
        Link New: This issue relates to JENKINS-50030 [ JENKINS-50030 ]

          oleg_nenashev Oleg Nenashev
          jimilian Alexander A
          Votes:
          0 Vote for this issue
          Watchers:
          4 Start watching this issue

            Created:
            Updated:
            Resolved: