Skip to content

Parallelize Nested Pipeline save #59

Description

@eyal-mor

Current implementation of the nested pipeline save uses a naive DFS implementation.

Meaning, each new pipeline stage & pipeline is saved sequentially.

For highly nested pipelines or pipelines with many stages this sequential save could cause performance issues.

To mitigate this problem, we should use a BFS approach and save pipelines siblings concurrently. This will mitigate the performance problems to some extent.

In addition, it might be wise to add logging in case of very nested pipelines (Depth > 3) to notify the developers of a possible issue.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Backend-SpinnakerThe issue is related to the built-in Spinnaker BackendenhancementNew feature or requestsaveRelated to "shore save"

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions