Performance Issues with multiple self-hosted steps in parallel

XMLWordPrintable

    • 2
    • Severity 2 - Major
    • 745

      Issue Summary

      Certain pipeline builds that use multiple self-hosted steps running in parallel are experiencing performance problems in the Bitbucket user interface. These issues can cause delays and page crashes.

      Steps to Reproduce

      1. Load the UI and navigate to a pipeline build that starts with a self-hosted runner step.
      2. Observe the performance issues when the page is loaded.

      Expected Results

      The UI should efficiently process logs without significant performance degradation.

      Actual Results

      The UI experiences performance issues due to excessive log processing, leading to crashes and slow response times.

      Workaround

      As a temporary workaround, rearrange the order of the parallel steps to prioritize non-runner steps first. This can help avoid loading a runner step first, which triggers the performance issues.

            Assignee:
            Unassigned
            Reporter:
            Bruno
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: