Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <3FA65A97.9090608@apache.org>
Date: Mon, 03 Nov 2003 08:39:35 -0500
From: Berin Loritsch <bloritsch@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.4) Gecko/20030624
MIME-Version: 1.0
To: Avalon Developers List <dev@avalon.apache.org>
CC: dev@cocoon.apache.org
Subject: Re: [IMP] Performance Killer and Memory leak
References: <OFCDCD2B8E.EB87D419-ONC1256DD2.0062F3EA@rz-c007-j650.basf-ag.de>
In-Reply-To: <OFCDCD2B8E.EB87D419-ONC1256DD2.0062F3EA@rz-c007-j650.basf-ag.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

volker.schmitt@basf-it-services.com wrote:


> The lookup/release add/remove the component to/from an ArrayList. If you
> have a lot of Components which lookup other Components inside the compose
> method the List can be really big. If you have a lot of SubSitemaps which
> use many InputModules it grows and grows ..... and the performance goes
> down and down ...

First: ArrayList is only helpful for small lists.  A better list type for
this case would be the LinkedList.

> Ok, but this is not the Killer. The Killer are Composable
> RequestLifecycleComponents, because they are usually lookuped from other
> Components using the ComponentManagerProxy but are released by the
> CocoonComponentManager which doesn't use the ComponentManagerProxy. What
> happen is, that they are not removed from the List, so the List explode.

This is a bug in COcoon's extension of the ECM project.  IT is something
that needs to be fixed.

Cocoon is welcome to update the ECM code in Excalibur if necessary.

-- 

"They that give up essential liberty to obtain a little temporary safety
  deserve neither liberty nor safety."
                 - Benjamin Franklin