You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2011/05/02 18:52:03 UTC

[jira] [Commented] (TAP5-1508) Reduce memory utilization of Tapestry page instances

    [ https://issues.apache.org/jira/browse/TAP5-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027721#comment-13027721 ] 

Howard M. Lewis Ship commented on TAP5-1508:
--------------------------------------------

With the changes for TAP5-853, the biggest remaining changes is to make use of ComponentClassTransformWorker2.

> Reduce memory utilization of Tapestry page instances
> ----------------------------------------------------
>
>                 Key: TAP5-1508
>                 URL: https://issues.apache.org/jira/browse/TAP5-1508
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.3.0
>            Reporter: Howard M. Lewis Ship
>
> This is an umbrella bug for a number of changes aimed at reducing the overall memory footprint of a Tapestry page.  Tapestry pages have been seen to be quite large in some production sites, and the shared-instance strategy introduced in 5.2 is still insufficient. A significant amount of space is consumed using Maps and Lists (for bindings, of sub-components, etc.) in a way that is optimized for a smaller code base and efficient read access, even though most of the information is only read when a page is first loaded, and is rarely needed or accessed after that.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira