[
https://issues.apache.org/jira/browse/MYFACES-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004839#comment-13004839
]
Mark Struberg commented on MYFACES-2634:
----------------------------------------
what happened with that? I think this already got implemented, isn't?
> 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
> Labels: gsoc, mentor
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
