-
Improvement
-
Resolution: Won't Fix
-
Minor
-
-
Pipeline - October, Pipeline - April 2018
As a user of pipeline, I WANNA GO FAST. 
One problem is that we have a bunch of mutable state attached to the WorkflowRun, and in the CpsFlowExecution, which results in constantly saving-and-re-saving the run, costing IO, CPU, and creating garbage to GC.
How do we fix that?
- Move the CpsFlowExecution fields heads and iota OUT and into either the program or the storage.
- May need to do some stuff in workflow-job plugin to accommodate the new impl – though it's created abstractly here – https://github.com/jenkinsci/workflow-job-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java#L263
[JENKINS-47174] Optimize incidental persistence calls during pipeline execution
Sam Van Oort
created issue -
Sam Van Oort
made changes -
| Epic Link | New: JENKINS-47170 [ 185575 ] |
| Sprint | New: Pipeline - October [ 406 ] |
| Sprint | Original: Pipeline - October [ 406 ] | New: Pipeline - October, Pipeline - December [ 406, 446 ] |
Sam Van Oort
made changes -
| Labels | Original: performance | New: performance project-cheetah |
| Sprint | Original: Pipeline - October, Pipeline - December [ 406, 446 ] | New: Pipeline - October, Pipeline - March 2018 [ 406, 506 ] |
Sam Van Oort
made changes -
| Resolution | New: Won't Fix [ 2 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
I think this is going to be pre-empted by other work we're doing – don't want to go into details yet until we're 100% settled on some parts of it, but it will be addressed from a radically different direction and I don't see the point in addressing it in the way described.