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

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on TAP5-1508:
------------------------------

Integrated in tapestry-trunk-freestyle #356 (See [https://builds.apache.org/hudson/job/tapestry-trunk-freestyle/356/])
    TAP5-1508: Get the right object from the InstanceContext, rather than use a down-cast
TAP5-1508: Optimize the @Import worker to initialize assets in the constructor, not on page load
TAP5-1508: Optimize the ClassInstantiatorImpl to not use a Map to store the instance context type/value pairs (since there's rarely more than one or two of them)

hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1130347
Files : 
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/transform/UnclaimedFieldWorker.java

hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1130338
Files : 
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/transform/ImportWorker.java

hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1130329
Files : 
* /tapestry/tapestry5/trunk/plastic/src/main/java/org/apache/tapestry5/internal/plastic/ClassInstantiatorImpl.java


> 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