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

Application startup time slow after Spring 4.0.x upgrade

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.5
    • Fix Version/s: 2.6
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-12988KC app startup time really slow with the latest rice 2.5 revision
      KULRICE-13070Pages load really slow after rice upgrade
      KULRICE-531development slowness
      KULRICE-3211Upgrade to Spring 3.0.1
      KULRICE-6724Override Spring class to improve startup performance
      KULRICE-11635Analyze upgrade to Spring 4.x
      KULRICE-8929KRAD rederning is slow due to Freemarker's FMParser initializing LookaheadSuccess multiple times
      KULRICE-4418cxf upgrade causes incorrect spring version to be brought in in client applications.
      KULRICE-2294Combine Rice Spring Contexts into a single Spring context
      KULRICE-6509Synchronize with remote services on KSB startup
    • Sprint:
      Rice Sprint 2015-02-18, Rice Sprint 2015-03-04, Rice Sprint 2015-03-18, Rice Sprint 2015-04-01
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes
    • Story Points:
      5

      Description

      KC reported KULRICE-12988 which indicated that the Spring 4.0.5 upgrade is very slow when fetching the views during

      DataDictionary.java
      generateMissingInquiryDefinitions();
      generateMissingLookupDefinitions();
      

      We added a workaround for KULRICE-12988 but still need to address the issue as to why this beta feature slowed down for this upgrade.

      Specifically, it seems that the calls like

      ddBeans.getBeansOfType(InquiryView.class).values();
      

      are the major holdup. Jerry noted that these have always been slow because we can't use the UIF index. We need to investigate why this is and how we can fix it so that startup times with a ton of views can be more efficient.

        Issue Links

          Activity

            People

            • Assignee:
              Brian Smith (Inactive)
              Reporter:
              Kristina Taylor (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Agile

                  Structure Helper Panel