-
Improvement
-
Resolution: Duplicate
-
Major
When loading Pipeline builds (WorkflowRuns) they eagerly load the FlowHeads, etc as part of deserialization. This triggers additional disk hits and initialization to create the FlowNodeStorage and populate it with those nodes.
We should lazy-load these for completed builds and avoid fetching heads until requested – this makes operations that iterate through builds much faster.
This is especially important because the Bulk FlowNode storage (https://issues.jenkins-ci.org/browse/JENKINS-47173) will load all the nodes when created – which will happen when loading the build. The CPU and disk hit for deserialization may be rather significant.
- duplicates
-
-
- Closed
-
- is related to
-
JENKINS-39489 Loading pipeline builds is expensive because they store scripts
-
- Open
-
- relates to
-
JENKINS-47173 Offer a high-performance storage engine for pipeline at some cost to resumability
-
- Closed
-
-
-
- Closed
-
[JENKINS-49086] Lazy-initialize FlowNodeStorage and heads, etc
Sam Van Oort
created issue -
Sam Van Oort
made changes -
| Epic Link | New: JENKINS-47170 [ 185575 ] |
Sam Van Oort
made changes -
| Link | New: This issue is related to JENKINS-39489 [ JENKINS-39489 ] |
Sam Van Oort
made changes -
| Labels | Original: performance pipeline | New: performance pipeline project-cheetah |
| Link |
New:
This issue relates to |
| Link |
New:
This issue relates to |
Sam Van Oort
made changes -
| Link |
New:
This issue duplicates |
Sam Van Oort
made changes -
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Sam Van Oort
made changes -
| Component/s | New: workflow-job-plugin [ 21716 ] | |
| Component/s | Original: workflow-cps-plugin [ 21713 ] |