Mailing-List: contact commits-help@tapestry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tapestry.apache.org
Date: Mon, 2 May 2011 23:52:03 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: commits@tapestry.apache.org
Message-ID: 
 <516675728.16802.1304380323679.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <621312040.64785.1303146245955.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (TAP5-1508) Reduce memory utilization of
 Tapestry page instances
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Integrated in tapestry-trunk-freestyle #334 (See [https://builds.apache.org/hudson/job/tapestry-trunk-freestyle/334/])
    TAP5-1508: Ensure that PlasticClass & friends are not accidentally leaked via inline inner classes


> 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