Details

    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-9794Reduce template invocations
      KULRICE-5010Improve role-member logic in RoleManagementServiceImpl.removePrincipalFromRole for performance
      KULRICE-10353Inline processing of FreeMarker templates
      KULRICE-5329Fix numeric comparisons on KEW identifiers that are no longer logical when those identifiers are Strings
      KULRICE-11678Rework base html template
      KULRICE-7208Template
      KULRICE-4131Fix backdoor login logic
      KULRICE-10545Review document search for lookup analysis items
      KULRICE-4829extract logic from IngesterAction
      KULRICE-746The ruleInstructions element must be defined on the ruleDefaults for Rule Template XML
    • 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

      Review all FTL templates to see what logic can be pulled out of the template and moved into code. Any statements (if, loop, etc.) are much more expensive to do in templates as opposed to code.

      Also, look into removing compression calls except for the one around the entire render. These are really expensive.

        Issue Links

          Activity

          Hide
          Mark Fyffe (Inactive) added a comment -

          Jerry,

          KULRICE-10353 was implemented based on analysis of existing freemarker tempaltes, and put together specifically for the purpose of moving high-volume logic (if/loop statements, high-traffic bean property lookups, etc) from templates to compiled code.

          Based on analysis of which templates had the biggest footprint, the following were converted from FreeMarker template code to inline Java code:

          • template.ftl
          • script.ftl
          • collectionGroup.ftl
          • stacked.ftl
          • groupWrap.ftl

          Further review and optimization of FreeMarker template logic, if needed, will be simplified by the inline template processing feature.

          Best,
          Mark

          Show
          Mark Fyffe (Inactive) added a comment - Jerry, KULRICE-10353 was implemented based on analysis of existing freemarker tempaltes, and put together specifically for the purpose of moving high-volume logic (if/loop statements, high-traffic bean property lookups, etc) from templates to compiled code. Based on analysis of which templates had the biggest footprint, the following were converted from FreeMarker template code to inline Java code: template.ftl script.ftl collectionGroup.ftl stacked.ftl groupWrap.ftl Further review and optimization of FreeMarker template logic, if needed, will be simplified by the inline template processing feature. Best, Mark

            People

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

              Dates

              • Created:
                Updated:

                Structure Helper Panel