[
https://issues.apache.org/jira/browse/MYFACES-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884260#action_12884260
]
Michael Concini commented on MYFACES-2780:
------------------------------------------
ah...sorry about that. I missed MYFACES-2764 or else I would've certainly
committed the refresh period change under that issue. Looks like conceptually
we were in agreement about the behavior during production though.
I would prefer to handle it as I've done in my update during factory creation
time so we only need to check the context param once and not with every
request. If you're ok with that, we can probably go ahead and resolve both of
these issues.
> 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
>
> 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.
