You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Mihir Solanki <mi...@patni.com> on 2005/04/29 07:26:15 UTC

OutOfMemory in tree2 node

Hi,

 

I am currently doing some kind of load testing for the tree2 component.

 

I have following kind of data in the tree.

 

1.                  One Root Node

2.                  10 Child nodes under the root node

3.                  Each child node has 5000 sub children

 

NOTE: All the data is coming through managed bean statically (i.e. no
interaction with the DB)

 

I am running this load testing application on tomcat 4.1.30.

When I request for the JSF page the tree is loading within around 1.8
seconds.

When I expand the ROOT node it is taking around 20 seconds.

When I expand the first child node (which is having 5000 children) after
around 25 seconds it is throwing OutOfMemory Error.

 

This scenario I have tested for three to four times and the result is same
for each time.

 

Can anybody have such kind of milestones for the tree2 component?

What should be the preferred data size for the tree2 component?

Can I take a risk to have tree2 component in the live projects where we have
a large chunk of data?

 

Please guide me as this is I guess very important thing for any enterprise
kind of application.

 

Thanks,

Mihir Solanki

  _____  

Patni Computer Systems Ltd.

Tel : 91 79 23240905 Ext : 413

 


http://www.patni.com
World-Wide Partnerships. World-Class Solutions.
_____________________________________________________________________

This e-mail message may contain proprietary, confidential or legally
privileged information for the sole use of the person or entity to
whom this message was originally addressed. Any review, e-transmission
dissemination or other use of or taking of any action in reliance upon
this information by persons or entities other than the intended
recipient is prohibited. If you have received this e-mail in error
kindly delete  this e-mail from your records. If it appears that this
mail has been forwarded to you without proper authority, please notify
us immediately at netadmin@patni.com and delete this mail. 
_____________________________________________________________________

Re: OutOfMemory in tree2 node

Posted by Sean Schofield <se...@gmail.com>.
That seems strange.  Even though you have a lot of nodes its still
only 50,000.  I assume you are using server-side toggle.  Is this
correct?  This might be a case where you would want to load the nodes
as you go (if you are not already doing that.)  Otherwise you might
run into some performance problems.  I still don't understand why you
would run into a memory issue though.

Right now the expand/collapse state is persisted in the client/side
state.  But its stored on an "as needed" basis.  The information is
only stored if you open a node.

My guess is that there is a memory leak somewhere in either the tree2
code or your code.  Off hand I can't think of where the problem would
be on tree2 end but its possible there is an issue.  Even if there
were a leak I wouldn't expect you to run out of memory after opening
only one or two nodes.  Are you sure you are running out of memory
after opening the first node a *single* time?

sean



On 4/29/05, Mihir Solanki <mi...@patni.com> wrote:
>  
>  
> 
> Hi, 
> 
>   
> 
> I am currently doing some kind of load testing for the tree2 component. 
> 
>   
> 
> I have following kind of data in the tree. 
> 
>   
> 
> 1.                  One Root Node 
> 
> 2.                  10 Child nodes under the root node 
> 
> 3.                  Each child node has 5000 sub children 
> 
>   
> 
> NOTE: All the data is coming through managed bean statically (i.e. no
> interaction with the DB) 
> 
>   
> 
> I am running this load testing application on tomcat 4.1.30. 
> 
> When I request for the JSF page the tree is loading within around 1.8
> seconds. 
> 
> When I expand the ROOT node it is taking around 20 seconds. 
> 
> When I expand the first child node (which is having 5000 children) after
> around 25 seconds it is throwing OutOfMemory Error. 
> 
>   
> 
> This scenario I have tested for three to four times and the result is same
> for each time. 
> 
>   
> 
> Can anybody have such kind of milestones for the tree2 component? 
> 
> What should be the preferred data size for the tree2 component? 
> 
> Can I take a risk to have tree2 component in the live projects where we have
> a large chunk of data? 
> 
>   
> 
> Please guide me as this is I guess very important thing for any enterprise
> kind of application. 
> 
>   
> 
> Thanks, 
> 
> Mihir Solanki 
>  ________________________________
>  
>  
> 
> Patni Computer Systems Ltd. 
>  
> 
> Tel : 91 79 23240905 Ext : 413 
> 
>   
> http://www.patni.com
>  World-Wide Partnerships. World-Class Solutions. 
> _____________________________________________________________________
>  
>  This e-mail message may contain proprietary, confidential or legally
> privileged information for the sole use of the person or entity to whom this
> message was originally addressed. Any review, e-transmission dissemination
> or other use of or taking of any action in reliance upon this information by
> persons or entities other than the intended recipient is prohibited. If you
> have received this e-mail in error kindly delete this e-mail from your
> records. If it appears that this mail has been forwarded to you without
> proper authority, please notify us immediately at netadmin@patni.com and
> delete this mail. 
> _____________________________________________________________________