Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-38363

Investigate slow loading experience

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Postponed
    • Icon: Major Major
    • blueocean-plugin
    • None
    • pacific, atlantic, 1.0-b05/b-06, arctic, tasman, frank

      When loading dogfood, or even locally, there is a noticable slowness in loading (can be seen as worm takes a while to cross the screen):

      This could be the result of the search api slowness (being addressed) or perhaps static resource inefficiencies: https://issues.jenkins-ci.org/browse/JENKINS-38253

      Investigating the causes of this (to confirm those other tickets) makes sense.

          [JENKINS-38363] Investigate slow loading experience

          Michael Neale created issue -
          Michael Neale made changes -
          Epic Link New: JENKINS-37957 [ 174099 ]
          Michael Neale made changes -
          Sprint New: 1.0-b05/b-06 [ 111 ]

          Michael Neale added a comment -

          kzantow if you could also take a look at https://issues.jenkins-ci.org/browse/JENKINS-38253 to help tom out, that would be appreciated.

          Michael Neale added a comment - kzantow if you could also take a look at https://issues.jenkins-ci.org/browse/JENKINS-38253 to help tom out, that would be appreciated.
          Michael Neale made changes -
          Assignee New: Keith Zantow [ kzantow ]

          Keith Zantow added a comment - - edited

          michaelneale I looked at this last week, the issue is mostly due to the API times. After some discussion with vivek fetching all the data using the traditional Jenkins object model results in reading a lot of data from disk, potentially including all the runs for all the jobs and more to find the latest and branch count, etc.. At a minimum, we can restrict it to the page asked for, ideally we can use some other optimizations to speed it up significantly more.

          Keith Zantow added a comment - - edited michaelneale I looked at this last week, the issue is mostly due to the API times. After some discussion with vivek fetching all the data using the traditional Jenkins object model results in reading a lot of data from disk, potentially including all the runs for all the jobs and more to find the latest and branch count, etc.. At a minimum, we can restrict it to the page asked for, ideally we can use some other optimizations to speed it up significantly more.

          Michael Neale added a comment -

          kzantow good to know, yes I suspected.

          Maybe shoudl leave this open as a place holder for any other investiation related to JENKINS-38253

          Michael Neale added a comment - kzantow good to know, yes I suspected. Maybe shoudl leave this open as a place holder for any other investiation related to JENKINS-38253
          Michael Neale made changes -
          Rank New: Ranked higher

          Michael Neale added a comment -

          kzantow as shown by Vivek, the slowness at least in the case of dogfood is NOT due to search and fetching of data from disk

          Michael Neale added a comment - kzantow as shown by Vivek, the slowness at least in the case of dogfood is NOT due to search and fetching of data from disk
          James Dumay made changes -
          Sprint Original: 1.0-b05/b-06 [ 111 ] New: 26-september, 1.0-b05/b-06 [ 101, 111 ]

            tfennelly Tom FENNELLY
            michaelneale Michael Neale
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: