Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 2.2
-
Fix Version/s: 2.3.1
-
Component/s: Development, User Experience (UX)
-
Security Level: Public (Public: Anyone can view)
-
Labels:None
-
Similar issues:
KULRICE-8448Improve Role Performance KULRICE-6735Document the Performance Improvements KULRICE-11177Need JPA related caching functionality to improve performance and support clustering KULRICE-14218 Release 2.3.7 with KRMS performance improvements KULRICE-9313Perform experiment on cloning for performance improvements KULRICE-10437Review LookupUtils for KRAD usage KULRICE-6557Improve Performance and Memory Consumption KULRICE-8918Improved KRAD collections performance KULRICE-12491Performance improvement for readXml in XmlHelper KULRICE-8956ComponentBase performFinalize Performance Improvement -
Epic Link:
-
Rice Module:KRAD
-
KRAD Feature Area:Utility
-
Sprint:2.3.1 Sprint 2
-
KAI Review Status:Not Required
-
KTI Review Status:Not Required
Description
LookupUtils' getSearchResultsLimit method acquires the search results limit from the view's spring configuration. View beans are prototypes, and each call requires spring to recreate the bean, or in the case of the object serialization performance fix, causes it to create a new object from the byte array cache.
Either way, this is quite a costly operation. The search results limit should probably be cached to avoid this work.
We believe that this is no longer an issue and has been changed