[
https://issues.apache.org/jira/browse/MYFACES-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886628#action_12886628
]
Leonardo Uribe commented on MYFACES-2780:
-----------------------------------------
I did two small enhancements:
- use FacesContext.isProjectStage().
- It is not really necessary to call FacesConfigurator.update and WebXml.update
on Lifecycle on the first request. The startup listener is the responsible to
configure everything.
There is an opportunity on
org.apache.myfaces.view.facelets.compiler.TagLibraryConfig. Basically
TagLibraryImpl has methods to add tag handlers, so we can do the same as the
proposal on ApplicationImpl.
> MyFaces performance improvements for production
> ------------------------------------------------
>
> Key: MYFACES-2780
> URL: https://issues.apache.org/jira/browse/MYFACES-2780
> Project: MyFaces Core
> Issue Type: Improvement
> Components: General
> Affects Versions: 2.0.0
> Reporter: Michael Concini
> Assignee: Michael Concini
> Priority: Minor
> Fix For: 2.0.1
>
>
> Several fixes to enhance startup memory footprint and runtime performance
> taking advantage of ProjectStage.
> -lazy loading of validators, converters, behaviors,components - can have a
> substantial impact on startup footprint in applications with multiple or very
> large widget libraries.
> Turn off some updating of resources for ProjectStage=Production by default
> (can always override using javax.faces.FACELETS_REFRESH_PERIOD)
> -change default facelets refresh interval to -1 when projectStage is
> production. This by itself gains a 60% improvement in throughput.
> -disable reloading of web.xml and faces-config after the first load.
> -store a map to cache Class to listenerFor and resourceDependency annotations
> when in production.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
