[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=13021374#comment-13021374 ] 

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

Integrated in tapestry-trunk-freestyle #319 (See [https://hudson.apache.org/hudson/job/tapestry-trunk-freestyle/319/])
    TAP5-1508: Strip out more tracking of file change timestamps when in production, except for asset resources, where tracking is needed to inform the client agent about the correct modification timestamp
TAP5-1508: Change ComponentPageelementImpl to use a simple List of child ComponentPageElements, rather than a Map or NamedSet
TAP5-1508: Disable the UpdateListenerHub and CheckForUpdatesFilter when in production mode
TAP5-1508: Create a mapping of nested component ids to component page elements, inside PageImpl
TAP5-1508: Add methods for extracting the values from a set, and null-safe static convenience methods
TAP5-1508: Add NamedSet.putIfNew() and NamedSet.create() methods
TAP5-1508: Add a simple and (hopefully) efficient NamedSet


> 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