-
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
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Closed
-
[JENKINS-38335] Search API too slow for dashboard
| Link |
New:
This issue relates to |
| Epic Link | New: JENKINS-35759 [ 171771 ] |
| Link |
New:
This issue blocks |
| Description |
Original:
*Search API (page limit 26)* * Took 7 sec on average * 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!) |
New:
*Search API (page limit 26)* * Took 7 sec on average * 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!) |
| Sprint | New: 1.0-b05/b-06 [ 111 ] |
| Description |
Original:
*Search API (page limit 26)* * Took 7 sec on average * 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!) |
New:
*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!) |
| Assignee | New: Vivek Pandey [ vivek ] |
| Rank | New: Ranked higher |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Description |
Original:
*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!) |
New:
*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 |