|
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 [EMAIL PROTECTED] and delete this mail. _____________________________________________________________________ |
- OutOfMemory in tree2 node Mihir Solanki
- Re: OutOfMemory in tree2 node Sean Schofield

