Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-33624

Improve performance of Pipeline Stage View even with very long FlowGraphs

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      The algorithms in pipeline stage view cover the normal use case well, but have issues with excessively large FlowGraphs. This is most commonly caused when someone runs a loop (with steps and/or blocks embedded in it) that executes many times.

      To reproduce, create and run a build with the following pipeline code and then view in stageview:

      for(int i=0; i<9999; i++) {
         echo "Cycle ${i}"
      }
      

      The result is combination of high master CPU load, very long or incomplete UI requests, very large response datasets (MB), and/or high memory use.

        Attachments

          Activity

          svanoort Sam Van Oort created issue -
          svanoort Sam Van Oort made changes -
          svanoort Sam Van Oort made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          svanoort Sam Van Oort made changes -
          Description The algorithms in pipeline stage view cover the normal use case well, but have issues with excessively large FlowGraphs. This is most commonly caused when someone runs a loop (with steps and/or blocks embedded in it) that executes many times.

          To reproduce, create and run a build with the following pipeline code and then view in stageview:
          for(int i=0; i<9999; i++) {
             echo "Cycle ${i}"
          }

          The result is combination of high master CPU load, very long or incomplete UI requests, very large response datasets (MB), and/or high memory use.
          3The algorithms in pipeline stage view cover the normal use case well, but have issues with excessively large FlowGraphs. This is most commonly caused when someone runs a loop (with steps and/or blocks embedded in it) that executes many times.

          To reproduce, create and run a build with the following pipeline code and then view in stageview:
          for(int i=0; i<9999; i++) {
             echo "Cycle ${i}"
          }

          The result is combination of high master CPU load, very long or incomplete UI requests, very large response datasets (MB), and/or high memory use.
          svanoort Sam Van Oort made changes -
          Description 3The algorithms in pipeline stage view cover the normal use case well, but have issues with excessively large FlowGraphs. This is most commonly caused when someone runs a loop (with steps and/or blocks embedded in it) that executes many times.

          To reproduce, create and run a build with the following pipeline code and then view in stageview:
          for(int i=0; i<9999; i++) {
             echo "Cycle ${i}"
          }

          The result is combination of high master CPU load, very long or incomplete UI requests, very large response datasets (MB), and/or high memory use.
          3The algorithms in pipeline stage view cover the normal use case well, but have issues with excessively large FlowGraphs. This is most commonly caused when someone runs a loop (with steps and/or blocks embedded in it) that executes many times.

          To reproduce, create and run a build with the following pipeline code and then view in stageview:

          {code:java}
          for(int i=0; i<9999; i++) {
             echo "Cycle ${i}"
          }
          {code}


          The result is combination of high master CPU load, very long or incomplete UI requests, very large response datasets (MB), and/or high memory use.
          svanoort Sam Van Oort made changes -
          Description 3The algorithms in pipeline stage view cover the normal use case well, but have issues with excessively large FlowGraphs. This is most commonly caused when someone runs a loop (with steps and/or blocks embedded in it) that executes many times.

          To reproduce, create and run a build with the following pipeline code and then view in stageview:

          {code:java}
          for(int i=0; i<9999; i++) {
             echo "Cycle ${i}"
          }
          {code}


          The result is combination of high master CPU load, very long or incomplete UI requests, very large response datasets (MB), and/or high memory use.
          The algorithms in pipeline stage view cover the normal use case well, but have issues with excessively large FlowGraphs. This is most commonly caused when someone runs a loop (with steps and/or blocks embedded in it) that executes many times.

          To reproduce, create and run a build with the following pipeline code and then view in stageview:

          {code:java}
          for(int i=0; i<9999; i++) {
             echo "Cycle ${i}"
          }
          {code}


          The result is combination of high master CPU load, very long or incomplete UI requests, very large response datasets (MB), and/or high memory use.
          svanoort Sam Van Oort made changes -
          Resolution Fixed [ 1 ]
          Status In Progress [ 3 ] Resolved [ 5 ]
          svanoort Sam Van Oort made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 169583 ] JNJira + In-Review [ 209844 ]

            People

            Assignee:
            svanoort Sam Van Oort
            Reporter:
            svanoort Sam Van Oort
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: