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

Long console output very slow to load after upgrade to LTS 2.246.1

      Since upgrade to  2.246.1, using various browsers and Oss, we face the same issue : a large log takes minutes freezing the current browser tab :

      • The log limitation is conform (only the end is loaded)
      • few lines appear
      • the tab is frozen during few minutes
      • the log is loaded and we can use the UI

      We provide screenshots of the flow

      Thnaks in advence

        1. lts1.png
          lts1.png
          82 kB
        2. LTS2.png
          LTS2.png
          113 kB

          [JENKINS-73710] Long console output very slow to load after upgrade to LTS 2.246.1

          Susan added a comment -

          the dreaded “loading spinner of eternity” when dealing with large console logs! Let’s tackle this slow console output issue in Jenkins after your upgrade to LTS 2.246.1.

          First off, you’re not alone—many Jenkins users have faced similar challenges. The good news is that there are some workarounds and solutions to improve this situation:

          Known Issue:
          What you’re experiencing is a well-known bug in Jenkins. It’s been reported and discussed by the community.
          Specifically, the issue you’re encountering is related to the delay in loading console output when dealing with large logs.
          The root cause lies in how Jenkins processes and displays console output, especially when there’s a substantial amount of data.
          Console Output Limit:
          Jenkins limits the console output displayed in the UI to prevent overwhelming the browser.
          By default, only the end of the log is loaded initially, which is why you see just a few lines.
          When you choose the “Show in Plain Text” option, it bypasses the UI rendering and displays the entire log immediately.
          External Log Storage:
          One recommendation to mitigate this issue is to use external log storage.
          Instead of relying solely on the Jenkins UI to display the entire console log, consider sending the logs to an external system (such as a log aggregator or SIEM).
          This way, you can retain the full log history without impacting the Jenkins UI responsiveness.
          Increasing Console Output Log Limit:
          While this won’t necessarily speed up the initial loading, it can help you retain more log data.
          You can increase the console output log limit in Jenkins. However, be cautious:
          Go to your Jenkins configuration (usually under “Manage Jenkins” > “Configure System”).
          Look for the setting related to console output log limit.
          Increase it to a value that suits your needs.
          Keep in mind that extremely large logs can still cause performance issues.
          Browser Considerations:
          Sometimes the browser itself can contribute to slow rendering.
          Ensure you’re using a modern browser with good performance characteristics.
          Clear your browser cache and try again.
          Patience and Optimism:
          While waiting for the log to load, consider practicing mindfulness or learning a new dance move. 
          In all seriousness, Jenkins is a powerful tool, but it does have its quirks. Keep an eye out for updates and improvements in future releases.

          Susan added a comment - the dreaded “loading spinner of eternity” when dealing with large console logs! Let’s tackle this slow console output issue in Jenkins after your upgrade to LTS 2.246.1. First off, you’re not alone—many Jenkins users have faced similar challenges. The good news is that there are some workarounds and solutions to improve this situation: Known Issue: What you’re experiencing is a well-known bug in Jenkins. It’s been reported and discussed by the community. Specifically, the issue you’re encountering is related to the delay in loading console output when dealing with large logs. The root cause lies in how Jenkins processes and displays console output, especially when there’s a substantial amount of data. Console Output Limit: Jenkins limits the console output displayed in the UI to prevent overwhelming the browser. By default, only the end of the log is loaded initially, which is why you see just a few lines. When you choose the “Show in Plain Text” option, it bypasses the UI rendering and displays the entire log immediately. External Log Storage: One recommendation to mitigate this issue is to use external log storage. Instead of relying solely on the Jenkins UI to display the entire console log, consider sending the logs to an external system (such as a log aggregator or SIEM). This way, you can retain the full log history without impacting the Jenkins UI responsiveness. Increasing Console Output Log Limit: While this won’t necessarily speed up the initial loading, it can help you retain more log data. You can increase the console output log limit in Jenkins. However, be cautious: Go to your Jenkins configuration (usually under “Manage Jenkins” > “Configure System”). Look for the setting related to console output log limit. Increase it to a value that suits your needs. Keep in mind that extremely large logs can still cause performance issues. Browser Considerations: Sometimes the browser itself can contribute to slow rendering. Ensure you’re using a modern browser with good performance characteristics. Clear your browser cache and try again. Patience and Optimism: While waiting for the log to load, consider practicing mindfulness or learning a new dance move.  In all seriousness, Jenkins is a powerful tool, but it does have its quirks. Keep an eye out for updates and improvements in future releases.

            Unassigned Unassigned
            fraifrai Frédéric
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: