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

Investigate acceptability of overall performance

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Minor Minor
    • blueocean-plugin
    • None

      As chatted about on various forums - an overview of the performance (web, resource loading, end to end) is needed to see if we have any blockers for a release candidate.

        1. screenshot-1.png
          screenshot-1.png
          47 kB
        2. screenshot-2.png
          screenshot-2.png
          44 kB
        3. screenshot-3.png
          screenshot-3.png
          117 kB

          [JENKINS-41735] Investigate acceptability of overall performance

          Ben Walding added a comment -

          I'll add my anecdotal data from a short investigation I did today.

          Using Chrome / Firefox, the web developer consoles say that BO is "ready" after 1.5s. However when I sit watching blueocean load - it's actually around 6s to a usable screen with my jobs loaded. It takes around 800ms to get the main page, and then 900ms to download the jobs. And if I sit watching the consoles, then there is an unexplained 3-4s delay after the jobs are downloaded where BO is "doing nothing", and then everything renders.

          In the screenshot above, the "idle" period is from 28000ms to 32000ms

          I also found (in a separate run - don't correlate to above) that scripting is showing up as a major consumer of time

          Obviously DOM manipulation has to be done - but I don't think I was expecting it to be such a heavy cost.
          (I have a modern MBP with 4 processors and 16GB of RAM)

          Enjoy this anecdote!

          Ben Walding added a comment - I'll add my anecdotal data from a short investigation I did today. Using Chrome / Firefox, the web developer consoles say that BO is "ready" after 1.5s. However when I sit watching blueocean load - it's actually around 6s to a usable screen with my jobs loaded. It takes around 800ms to get the main page, and then 900ms to download the jobs. And if I sit watching the consoles, then there is an unexplained 3-4s delay after the jobs are downloaded where BO is "doing nothing", and then everything renders. In the screenshot above, the "idle" period is from 28000ms to 32000ms I also found (in a separate run - don't correlate to above) that scripting is showing up as a major consumer of time Obviously DOM manipulation has to be done - but I don't think I was expecting it to be such a heavy cost. (I have a modern MBP with 4 processors and 16GB of RAM) Enjoy this anecdote!

          Michael Neale added a comment -

          bwalding have you tried a water cooling CPU? just use a hose.

          Michael Neale added a comment - bwalding have you tried a water cooling CPU? just use a hose.

          Keith Zantow added a comment -

          At first, I thought this was coming from a Raspberry PI...

          Keith Zantow added a comment - At first, I thought this was coming from a Raspberry PI...

          Ben Walding added a comment -

          I use vegemite as thermal paste.

          Ben Walding added a comment - I use vegemite as thermal paste.

          Michael Neale added a comment -

          Of course an Australian (who lives near me) already tried that: http://www.dansdata.com/goop.htm

          Michael Neale added a comment - Of course an Australian (who lives near me) already tried that: http://www.dansdata.com/goop.htm

          Michael Neale added a comment -

          From what Ben is saying this seems to get worse with more Favourites (which is odd, I could understand they would be slow to serve, but to render?)

          Michael Neale added a comment - From what Ben is saying this seems to get worse with more Favourites (which is odd, I could understand they would be slow to serve, but to render?)

          Ben Walding added a comment -

          Well my theory - it was just the volume of items on the page causing the delay - it didn't seem like favourites were exponentially worse than the normal jobs that were displayed on first load.

          Ben Walding added a comment - Well my theory - it was just the volume of items on the page causing the delay - it didn't seem like favourites were exponentially worse than the normal jobs that were displayed on first load.

            Unassigned Unassigned
            michaelneale Michael Neale
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: