First thing I'd suggest; Turn off debug mode!!!!! It seems a chunk of the Gced objects are coming from preparing strings for log statements which are only activated when debug mode is on (for example; Com.opensymphony.xwork2.util.InstantiatingNullHandler.nullPropertyValue(Map, Object, Object) accounts for 5% of Gced objects, of which nearly the entire 5% comes from StringBuilter and Log4JLoggerdebug which are only used when debug mode is on).
Secondly it does seem as though there's anything wildly wrong here, there aren't any single methods which have large Gced object counts indicating there isn't a big bottleneck (yes, some show 30+%, but that's fairly evenly divided between the methods called by the 30+% method), which leads me to one question, how much data are you trying to output? Can you do a "Save Source" and tell me the size of the HTML file generated?, can you also provide the call tree with a call count so we can see how many times the methods are being executed? Thanks, Al. -----Original Message----- From: Ing. Andrea Vettori [mailto:[EMAIL PROTECTED] Sent: 25 June 2007 09:35 To: Struts Users Mailing List Subject: Re: [S2] App generate lot (2GB) of garbage! Il giorno 25/giu/07, alle ore 09:50, Al Sutton ha scritto: > Your trace is at too higher level. Can you put a fully expanded copy > of your trace that goes down to the leaf methods. Done. It's on traceall.html. I expanded only the two most garbage producing top call. Thank you -- Ing. Andrea Vettori Consulente per l'Information Technology --------------------------------------------------------------------- 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]
