Details

      Description

      Current Situation

      • Performance when displaying logs by the JOC Cockpit log view window is unsatisfactory
      • Trying to display a log with e.g. 7MB causes the JOC Cockpit to hang
      • Displaying larger logs requires to adjust memory settings for the web service, see JOC-435

      Desired Behavior

      • Provide a clear statement about the guaranteed performance when displaying logs
        • response time in relation to log size (200KB, 2MB, 10MB)
        • max. log size for display with JOC Cockpit, e.g. 10MB
      • Analyze and Improve performance. JOC Cocmpit should be able to display logs of up to 10MB size. For larger logs the solution as indicated with JOC-435 can apply.

        Issue Links

          Activity

          Hide
          Oliver Haufe added a comment - - edited

          HI Sourabh Agrawal,
          ok, yes, I'm understand. The window.open is not directly called after a user action.

          What happens if you call ./log/info synchron without a callback?
          Can it make a difference?

          Show
          Oliver Haufe added a comment - - edited HI Sourabh Agrawal , ok, yes, I'm understand. The window.open is not directly called after a user action. What happens if you call ./log/info synchron without a callback? Can it make a difference?

            People

            • Assignee:
              Sourabh Agrawal
              Reporter:
              Andreas Püschel
              Approver:
              Oliver Haufe
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: