tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-1508) Reduce memory utilization of Tapestry page instances
Date Tue, 03 May 2011 22:21:03 GMT

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

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

Integrated in tapestry-trunk-freestyle #335 (See [https://builds.apache.org/hudson/job/tapestry-trunk-freestyle/335/])
    TAP5-1508: Revise how PlasticManager is created, rebuild relationship between ComponentClassResolver
and ComponentInstantiatorSource


> 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

Mime
View raw message