Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Message-ID: <1770880908.567471269909687173.JavaMail.jira@brutus.apache.org>
Date: Tue, 30 Mar 2010 00:41:27 +0000 (UTC)
From: "Martin Marinschek (JIRA)" <dev@myfaces.apache.org>
To: dev@myfaces.apache.org
Subject: [jira] Created: (MYFACES-2634) MyFaces 2.0 performance improvements
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

MyFaces 2.0 performance improvements
------------------------------------

                 Key: MYFACES-2634
                 URL: https://issues.apache.org/jira/browse/MYFACES-2634
             Project: MyFaces Core
          Issue Type: New Feature
          Components: JSR-314
            Reporter: Martin Marinschek
            Assignee: Martin Marinschek


JSF 2.0 introduced a partial state saving option: state of the page will not completely, but only partially state-saved.

This partial state saving reduces the page-state memory to around 20% of the value under the JSF 1.2 full state saving option, as preliminary measurements show - this is a relevant reduction.

However, I believe we can reduce this number even more, if we carefully take a look on what really needs to be saved and how.

This project would need to provide:

1) a setup to measure the numbers and provide comparisons
2) measurements of the current state
3) several steps which lead to a reduction of the state

Further research topics could be:

- partial state-saving in tables - currently, this is not implemented at all
- if no c:if, c:forEach, or ui:include is present on the page, we could get rid of the second application of the template before rendering automatically.

best regards,

Martin

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.