-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
-
pacific, atlantic, 1.0-b05/b-06
Search API (page limit 26)
- Took 7 sec on average (in other cases, 12seconds for 11kb of data - from bwalding)
- To address sorting by name and exclude certain items from flattening all possible items are loaded in memory
- jenkins.getAllItems()
- Exclude items that are children of multi-branch and matrix project
- Don’t see how we can avoid it unless the jobs are stored in some kind of db with indexed column to speed up sorting and only give limited records instead of all
- new PipelineContainerImpl().getPipelines(items) should be pagination aware
- At present it creates BluePipeline object for all possible items (ouch!)
Also: check that runs/activity benefits from same pagination aware optimisation
- blocks
-
JENKINS-38079 Investigate performance degradation report
- Closed
- is blocked by
-
JENKINS-38981 Eliminate expensive calculation of running builds
- Closed
- is duplicated by
-
JENKINS-38087 initial search call extremely slow
- Closed
- relates to
-
JENKINS-38087 initial search call extremely slow
- Closed