<P>I agree that this is completly application dependent.</P><P>The fact is that we guess these parameters, without knowing the need. A good thing is to let a particular application uses its own values.</P><P>Phil. <BR><BR><FONT SIZE=2><B>Dennis Sosnoski <dms@sosnoski.com></B></FONT><BR><FONT SIZE=2>05/28/2003 09:32 AM MST</FONT><BR><BR> <FONT SIZE=2>To:</FONT> <FONT SIZE=2>Alex Rosen <arosen@novell.com></FONT><BR> <FONT SIZE=2>cc:</FONT> <FONT SIZE=2>jdom-interest@jdom.org, phil@triloggroup.com</FONT><BR> <FONT SIZE=2>bcc:</FONT> <BR> <FONT SIZE=2>Subject:</FONT> <FONT SIZE=2>Re: [jdom-interest] About FastFactory</FONT><BR> <BR><BR></P><P><FONT FACE="Monospace,Courier">Anything with the list sizes is going to be heavily dependent on the<BR>structure of the data. The much_ado.xml that you mention, Phil, is the<BR>marked-up text of the play. periodic.xml is from Elliotte, and has a lot<BR>of children of the root (for individual elements) with each child also<BR>having many children (characteristics of the element). Both are shallow<BR>but wide, so they may be atypical.<BR></FONT><BR><FONT FACE="Monospace,Courier">Is JDOM handling the list growth directly? If so, I think starting with<BR>something like 4 or 5 and doubling each time you run out of room is<BR>likely to give reasonable results.<BR></FONT><BR><FONT FACE="Monospace,Courier"> - Dennis<BR></FONT></P>