[KULRICE-8431] Performance: perform expression function setup only once per lifecycle Created: 21/Oct/12  Updated: 01/Nov/13  Resolved: 21/May/13

Status: Closed
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: None
Fix Version/s: 2.3
Security Level: Public (Public: Anyone can view)

Type: Task Priority: Critical
Reporter: Jerry Neal (Inactive) Assignee: Jerry Neal (Inactive)
Resolution: Complete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
cloned from KULRICE-7208 Template Closed
cloned to KULRICE-8432 Peformance: remove default readOnly e... Closed
discovered by KULRICE-6557 Improve Performance and Memory Consum... Closed
Similar issues:
KULRICE-8468Performance: Collect templates through view lifecycle and include once in view rendering
KULRICE-9313Perform experiment on cloning for performance improvements
KULRICE-1130improve performance of xml ingestion
KULRICE-13490Update Performance environment setup
KULRICE-13147Inefficiencies in view lifecycle and rendering
KULRICE-10980Analysis on performance tasks
KULRICE-9866Performance issue in calculate message totals on client
KULRICE-9597Script logic performance pass
KULRICE-7220Look into replacing component update process with full view lifecycle
KULRICE-8798Look into multithreading during the view lifecycle
Rice Module:
KAI Review Status: Not Required
KTI Review Status: Not Required
Include in Release Notes?:


Expression functions are setup for each expression evaluation. Performance can be improved by only setting up these once per lifecycle

Comment by Jerry Neal (Inactive) [ 06/Feb/13 ]

From Dan:

Another place for speed improvement is in the ExpressionEvaluatorServiceImpl. This gets called a lot. Something small that could speed things up is use a static parser and also cache the parsed expressions.

Generated at Wed Jun 03 11:07:13 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.