Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-10093

Validation framework performance problem with writeMessagesForPage recursion

    Details

    • Type: Task Task
    • Status: Open Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: 2.3
    • Fix Version/s: Backlog
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-8081Problem with 'no tooltips' in validation framework demo
      KULRICE-10091Performance problem with validation script on ajax details
      KULRICE-5127Fix infinite recursion problem w/ GlobalResourceLoaderServiceFactoryBean
      KULRICE-5161treeNode.tag exhibits recursive tag problem on Linux in Jetty 7.4.1
      KULRICE-5281UIF Framework - Develop UifValidationService that will do validation
      KULRICE-1445inconsistency in errors paths for recursive dd validation
      KULRICE-9903Validation Framework alerts for ARIA tags
      KULRICE-9866Performance issue in calculate message totals on client
      KULRICE-6743Document the UI Framework - State-based Validation
      KULRICE-3538Maintenance Doc does not recursively run DD validation for BO when routing
    • Epic Link:
    • Rice Module:
      KRAD
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      There still exists a performance problem with the crawling up from something that was just refreshed to the rest of the parents, if the thing that is refreshed has messages. This is due to the calculation of the output that must be generated due to changes in either removing messages, or adding messages through the refresh.

      There has already been a good amount of time spent in this area. Many improvements were already made to help with the performance issue, but it can still become a problem in deeply nested groups which change the message state. I have already tried one solution based on the visitor pattern so I wouldn't have to do some calculations but it was too heavyweight and became slower overall.

      Much of the time spent (I think) currently is the calculation of totals to update dynamically and the dom manipulation to update dynamically.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Brian Smith (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Structure Helper Panel