Comes from DOM itself. Not Cocoon's fault. It makes sense if you consider a DOM tree may grow roughly 10 times the original doc size...
----- Original Message ----- From: "David LAGARDERE" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, October 16, 2003 1:58 PM Subject: Cocoon And Memory > Hello. > > I 've been working with Cocoon 2.0 for one year and a > half now and I still don't understand why so much > memory is needed. Moreover, I haven't found any > relevant piece of information about requirements > issued by the Cocoon development team. The performance > tips web page does not help in this case. > As an example, consider a 12 Mb document resulting > of the aggregation of five smaller documents : the > whole processing ending up by an XSLT transformation > (one template) makes my JVM grow up from 150 Mb to > 350Mb. I know that most of it will be finally garbaged > but this is not my consideration. My question is : > where does this 200Mb come from ? Does version 2.1 > improves this behaviour ? > Any help will be greatly appreciated. > > Thanks > > David LAGARDERE > > ___________________________________________________________ > Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran�ais ! > Yahoo! Mail : http://fr.mail.yahoo.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
