Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Message-ID: <23367138.213081278408051770.JavaMail.jira@thor>
Date: Tue, 6 Jul 2010 05:20:51 -0400 (EDT)
From: "Martin Marinschek (JIRA)" <dev@myfaces.apache.org>
To: dev@myfaces.apache.org
Subject: [jira] Commented: (MYFACES-2780) MyFaces performance improvements
 for production
In-Reply-To: <18183155.140841277929550153.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MYFACES-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885474#action_12885474 ] 

Martin Marinschek commented on MYFACES-2780:
--------------------------------------------

Hi guys,

how is lazy loading good for production performance? In production, I would expect everything to be initialized on startup - so that request times are as low as possible (and certainly not the first request is taking longer than all other requests). Startup is not so much an issue in production! That's why everyone precompiles JSPs in production.

best regards,

Martin

> 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.