Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Invalid
-
Affects Version/s: 1.7
-
Fix Version/s: None
-
Component/s: Framework
-
Labels:None
-
Environment:ICEfaces
Description
phases. By profiling test applications and comparing the results
against stock JSF, the hotspots will be revealed, allowing us
to concentrate our efforts on the code requiring performance
optimizations. We must beware, however, as some of the hotspots
will be inherent JSF CPU sinks, giving no opportunity for
optimization.
Poor synchronization may lead to poor performance, and ICEfaces
definitely applies more synchronization than stock JSF. We
should look at each usage of synchronization to see if it is
necessary and ensure that it rarely spans user sessions.
How much CPU time is spent in each of the following phases?
Initialization
- does init occur exactly as necessary; i.e. we should
make sure we're not parsing the page on every request
JSP parsing
Facelets parsing
Output
lifecycle.execute()
lifecycle.render()
component tree traversal
- hot spots within components
DOM diff
DOM serialization
receive-updates
JMS update propagation
Input
restore view
decode
events
Issue Links
- depends on
-
ICE-3729 Components use attributesThatAreSet
- Closed
-
ICE-3300 Framework algorithm improvements in passThroughAttribute and DOMSerialization areas
- Closed
-
ICE-3321 Create a outputText and inputText component that uses ResponseWriter instead of DOMContext
- Closed
-
ICE-3346 Pass-through Attribute Optimization and Rationalization
- Closed
-
ICE-3387 serialize DOM directly to writer
- Closed
-
ICE-3393 Eliminate unnecessary UIComponent.getChildren() calls
- Closed
-
ICE-3730 Optimise UIComponent.getRenderer() accesses
- Closed
-
ICE-3731 Optimise DOMResponseWriter.enhanceBody
- Closed
-
ICE-3732 Optimise BridgeFacesContext.applyBrowserDOMChanges()
- Closed
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Marking as Closed / Invalid as part of legacy ICEfaces 1.x, 2.x JIRA cleanup.
Note: This issue may be resolved in a newer ICEfaces release, available here: http://www.icesoft.org/java/downloads/icefaces-downloads.jsf
If the issue persists with the current ICEfaces release, please create a new JIRA for it.