Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.7.1
-
Fix Version/s: 1.7.2
-
Component/s: Framework, ICE-Components
-
Labels:None
-
Environment:ICEfaces
-
ICEsoft Forum Reference:
Description
Rendering performance in applications is always a concern, but a clients Facelets application illustrated particularly poor rendering performance.
https://www.icesoft.ca:4443/supportilla/show_bug.cgi?id=4903
First notably were two methods on top of the profiling time lists. The serialize method of the DOMSerilizer class, and the renderNonBooleanAttributes method of the PassThroughAtrributeRenderer both have some questionable code. It might be justifiable but it seems very expensive.
This bug should be used to track any changes made to the framework and components with respect to this application.
https://www.icesoft.ca:4443/supportilla/show_bug.cgi?id=4903
First notably were two methods on top of the profiling time lists. The serialize method of the DOMSerilizer class, and the renderNonBooleanAttributes method of the PassThroughAtrributeRenderer both have some questionable code. It might be justifiable but it seems very expensive.
This bug should be used to track any changes made to the framework and components with respect to this application.
Issue Links
- blocks
-
ICE-3082 CPU performance/efficiency
-
- Closed
-
The serialize method no longer show up on the top of the profiling lists, and for the clients application in question, this results in a large reduction in the number of method calls. This doesn't necessarily result in a large realtime improvement (roughly 10% in the app in question, eg. 1/10's of seconds on my development machine) but the change will definitely effect scalability in this type of application with large, changing, data sets.
Much more improvement in rendering speed occurs with changes to the pass through attribute rendering http://jira.icefaces.org/browse/ICE-3346