I don't know much about jprofiler, but in general, it would be good to see where most of the processing time is being taken up.
I'm going to leave the rest of this to someone else (Matt?) since I don't know Velocity very well... > -----Original Message----- > From: Drew McAuliffe [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 07, 2003 1:47 PM > To: [EMAIL PROTECTED] > Subject: [OS-webwork] RE: Performance diff bw ww1 and ww2? > > > Sure, I have jprofiler hooked up to my Tomcat install. The > thing is, I'm a little ignorant with it. I'll play around and > see what kind of data I can produce. Any tips on how to get > what you need would be > appreciated.:) Also, here are some samples from the macros > that do a lot of the work in my app. In ww1, #macro(bean > $bean_name $name) > #set ($name = $webwork.bean($bean_name)) > #end > > #macro(url $name) > #set ($name = $webwork.bean("webwork.view.velocity.URLBean")) > $name.setRequest($req) > $name.setResponse($res) > #end > > #macro(property $object $property) > #bean("com.scea.core.web.support.VelocitySafeBeanUtils" $bu) > $!{bu.getProperty($object, $property)}#end > > #macro(evaluate $expression) > $webwork.evaluate($expression)#end > > For ww2, > #macro(bean $bean_name $ref) > #set ($ref = $stack.findValue("new $bean_name()")) > #end > > #macro(url $name) > #bean("com.scea.core.web.support.VelocityUrlBean" $name) > $name.setRequest($req) > $name.setResponse($res) > #end > > #macro(property $object $property) > $!{ognl.findValue($property, $object)}#end > > #macro(evaluate $expression) > $expression#end > > I've turned off the "evaluate" macro in ww2 because I was > concerned with its performance. I'm not sure what to use to > replace it, except maybe "$stack.findValue()", though I don't > know if that's a perfect analogue to $webwork.evaluate(), > which does a velocity parse rather than an ognl parse. I > don't know which would be faster. In ww2, I had to create a > copy of the URLBean from ww1 because I couldn't find a ww2 > equivalent. The velocity tag support only seems to work for > UI tags (from what I can see in the source) and besides, > calling a tag to call an underlying velocity script to put > data into another velocity script seems like overkill, > performancewise. Note that I'm not using any of the UI tags > in my code and I'm still running into performance issues. > Also, at latest check, my view page load times are averaging > anywhere from 250 - 350 ms, which is about a tenfold increase > in time. I'm torn because I need performance but I also need > something that ww2 has the ww1 doesn't, which is the ability > to parse multiple checkbox values into an array or collection > property on an action (if that can be done with ww1 I might > switch back but I've had no luck). > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites > including Data Reports, E-commerce, Portals, and Forums are > available now. Download today and enter to win an XBOX or > Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet _072303_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
