[JIRA] (JENKINS-60980) Job status screen slows as stage count increases, becomes unusable

3 views
Skip to first unread message

jerrywiltse@gmail.com (JIRA)

unread,
Feb 5, 2020, 9:56:04 AM2/5/20
to jenkinsc...@googlegroups.com
jerry wiltse created an issue
 
Jenkins / Bug JENKINS-60980
Job status screen slows as stage count increases, becomes unusable
Issue Type: Bug Bug
Assignee: Unassigned
Components: core
Created: 2020-02-05 14:55
Priority: Minor Minor
Reporter: jerry wiltse

We have functional jobs which enumerate lists and spawn parallel stages for each item in the list.  We have several which run 100+ tests.  

The load speed and page width of the built-in job status/summary screen scales really poorly with the number of stages.  The page width is ugly after just 10 stages, and the performance becomes a problem around 50 (depending on the resource of the machine). Over 300, it can become unusable and can crash browser, especially when multiple tabs are open. The blue-ocean plugin is certainly better, but it's still a problem with the official jenkins UI, so i'm reporting it.

From a UI perspective, I'm sure there are a number of simple ways to resolve these two issues without an overhaul of the whole page, and without breaking backward compatibility.  I will suggest one, it may be a terrible one, but my org really wants these problems to be fixed.

Add a section in Manage Jenkins somewhere for global GUI setting defaults.  I'm surprised nothing like this exists already.  Add "max stages" setting in that section.  Have the job status/summary page check that setting, and only load that many stages while rendering the page.  Add a "show all stages" button to that page when rendering pages which exceeded this max. 

Also of note, I am going to open another ticket about default view rendering of the pipeline_steps view which also scales very poorly when nesting many jenkins functions. I think this could also benefit from having a number of relevant settings in a new "global gui setting defaults" section.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages