On Wed, 27 Mar 2002, Kin-Man Chung wrote: > Pulling codes out of iteration tag bodies is very high on my list of > optimizations that I wnat to do. I don't think we can do much about > general scriplets that contain loops, though. > > But before we start on jasper optimization work, we'll need benchmarks > and performance analysers. I have learnt from experience that performance > improvement often comes from surprising places, and that optimizations > done at the wrong time and place often do more harm than good. Benchmarks > would give us some real metric for us to measure our optimization work, > and analyzing tools would let us identify hot spots that need to be improved. > > I'd appreciate comments, suggestions, and pointers on these two subjects. > I'd also appreciate if anyone can donate some real life applications that > I can use for benchmarking jasper performance.
The most usefull tools are OptimizeIt and ab. Simple pages would help much better then complex pages - first find out what's the overhead of executin a simple JSP page, with no tags, compare it with the equivalent servlet ( HelloWorld ), and find out what's wrong. Then use a simple hello world Tag, compare it with the equivalent servlet ( or JSP not using tags ), and find what's wrong. Same for a simple iteration tag, compared with a scriptlet If you solve those simple problems, and get the tag version in a reasonable limit, I think we'll all be very happy ( 30% slower would be acceptable for me, even 1/2 the speed of the equivalent scriptlet ). Going after 'real life applications' when the simple hello world tag, or a simple empty jsp page has a clear performance penalty would be a waste of time. ( all that with a reasonable load - I sugest 80 concurent requests ) Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
