Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Blocker Blocker
    • Resolution: Complete
    • Affects Version/s: None
    • Fix Version/s: 2.0.0-rc1, 2.0
    • Component/s: Performance, Unit Testing
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-9215Multi row col span overwritten in TableLayoutManager
      KULRICE-13448Investigate Rice sampleapp out of memory exceptions
      KULRICE-8748Set TableLayoutManager applyDefaultCellWidths to false by default
      KULRICE-13157AFT Failure DemoLookUpStackedResultsAft ClassCastException StackedLayoutManagerBase cannot be cast to TableLayoutManager
      KULRICE-6585Look into possible memory and thread local leaks reported by tomcat on a shutdown
      KULRICE-13293Prepare CI for 2.5 Release
      KULRICE-9280Split Release Documentation into module-based books
      KULRICE-6557Improve Performance and Memory Consumption
      KULRICE-9589Add documentation notes for KRAD Phase 3 items to Release Notes
      KULRICE-13313Increase env12 and env14 AFT timeouts for release testing
    • Rice Module:
      KRAD
    • Application Requirement:
      KS My Plan
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      Based on an email from Kamal Muthuswamy below...

      MyPlan team ran into some early performance issues while searching for courses and displaying them using KRAD. We are running out of memory (1Gb) in two search runs with 800 records itself. In all cases I see that the code moves to KRAD rendering of view component and then hangs.

      From some basic YourKit profiling, I see TableLayoutManager in one instance going all the way utpo 400Mb.

      I do see the memory being released eventually but not all of it, after each run. I am willing to show the problem and also help do some additional profiling if you think that will be usefull.

        Issue Links

          Activity

          Hide
          Jessica Coltrin (Inactive) added a comment -

          setting to review in rc1. according to scott, There was some email discussion over the break about it and most of the talk was some fairly large design changes. I think this should be an rc1 issue and I just want to reiterate my warning about it: it is unclear whether there is an actual bug here or not. KNS/KRAD applications limit lookup results to something like 3-5 hundred (it's configurable). MyPlan is sending unlimited results to the screen to do javascript filtering (the facet stuff). Supporting unlimited lookup results is not in the krad design and at the meeting we had with MyPlan everyone agreed that this was not a practical approach - so what they are doing is a stop gap until some server side krad support can be delivered.

          We'll also be discussing at the Leads meeting this week.

          Show
          Jessica Coltrin (Inactive) added a comment - setting to review in rc1. according to scott, There was some email discussion over the break about it and most of the talk was some fairly large design changes. I think this should be an rc1 issue and I just want to reiterate my warning about it: it is unclear whether there is an actual bug here or not. KNS/KRAD applications limit lookup results to something like 3-5 hundred (it's configurable). MyPlan is sending unlimited results to the screen to do javascript filtering (the facet stuff). Supporting unlimited lookup results is not in the krad design and at the meeting we had with MyPlan everyone agreed that this was not a practical approach - so what they are doing is a stop gap until some server side krad support can be delivered. We'll also be discussing at the Leads meeting this week.
          Hide
          Kamal Muthuswamy (Inactive) added a comment -

          Scott: I don't think it is the unlimited lookup issue. We are open to keeping the number of results limited to some acceptable number. But right now the bug is that even if it is 300 - 400 records a couple of users hitting the system within a short interval will bring down the system. I think that is unacceptable.

          Right now for input field we see a 41K per cell in the table and so for a table with 400 records with 7 columns will put 115 Mb in the user session so u can see that 10 - 20 users using search will basically take down the system. I haven't done metrics with DataField but even there the numbers are not expected go down significantly.

          Show
          Kamal Muthuswamy (Inactive) added a comment - Scott: I don't think it is the unlimited lookup issue. We are open to keeping the number of results limited to some acceptable number. But right now the bug is that even if it is 300 - 400 records a couple of users hitting the system within a short interval will bring down the system. I think that is unacceptable. Right now for input field we see a 41K per cell in the table and so for a table with 400 records with 7 columns will put 115 Mb in the user session so u can see that 10 - 20 users using search will basically take down the system. I haven't done metrics with DataField but even there the numbers are not expected go down significantly.
          Hide
          Scott Gibson (Inactive) added a comment -

          This needs to be looked at in terms of session management of the data for 2.0. In a later version we can address size of form/view elements.

          Show
          Scott Gibson (Inactive) added a comment - This needs to be looked at in terms of session management of the data for 2.0. In a later version we can address size of form/view elements.
          Hide
          Jessica Coltrin (Inactive) added a comment -

          setting to blocker since it's blocking My Plan load testing.

          Show
          Jessica Coltrin (Inactive) added a comment - setting to blocker since it's blocking My Plan load testing.
          Hide
          Jerry Neal (Inactive) added a comment -

          Resolving this issue for rc1 with the update, and will create another issue and link for ongoing work in rc2

          Show
          Jerry Neal (Inactive) added a comment - Resolving this issue for rc1 with the update, and will create another issue and link for ongoing work in rc2
          Hide
          Jessica Coltrin (Inactive) added a comment -

          Closing since these items are now in the release notes.

          Show
          Jessica Coltrin (Inactive) added a comment - Closing since these items are now in the release notes.

            People

            • Assignee:
              Jerry Neal (Inactive)
              Reporter:
              Matt Sargent
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel