Hi Paolo, Thanks for taking the time to profile Webwork. See more comments inline...
----- Original Message ----- From: "Vedovato Paolo" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, February 06, 2004 9:43 AM Subject: RE: [OS-webwork] WW1.3 Memory Consumption > Hi Hani > > I just let my application run with WW1.4 (CVS 3 feb 04) > and the problem is exact the same as in WW1.3 with one > difference that not only Query and QuerySegment grow > when using the table tag but now also > webwork.util.ConcurrentReaderHashMap$Entry grows with > the same amount. > I guess your profiling only shows webwork classes. The memory you see for ConcurrentReaderHashMap$Entry was probably the same in WW1.3 only that then a java.util.HashMap was used instead so it does not show in your profiling. > BTW: since I'm into profiling: > I saw that ValueStack$MethodInfo came in in WW1.4. > It's a big (!) memory holder which never gets GC'ed... > Overall it seems to me that WW1.4 uses a lot more memory than > 1.3... > MethodInfo was introduced in order to improve performance when calling methods through the value stack (I posted some figures on the measured improvement a loooong time ago, so I don't remember them now). There were other performance improvements as well, some at the expense of memory consumption, for example the SimpleTest class that shows up in your chart. They should all more or less be static, so for a given application they should not grow over time. (I have not had the time to look at your code for the table tag yet). Do you, or anyone else think this is a big problem? Cheers, Dick Zetterberg ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
