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. Thanks in advance. - Kin-man > Date: Wed, 27 Mar 2002 15:31:54 -0600 > From: Casey Lucas <[EMAIL PROTECTED]> > Subject: Re: tag pooling question > To: Tomcat Developers List <[EMAIL PROTECTED]> > MIME-version: 1.0 > Content-transfer-encoding: 7bit > X-Accept-Language: en > Delivered-to: mailing list [EMAIL PROTECTED] > Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm > X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > List-Post: <mailto:[EMAIL PROTECTED]> > List-Subscribe: <mailto:[EMAIL PROTECTED]> > List-Unsubscribe: <mailto:[EMAIL PROTECTED]> > List-Help: <mailto:[EMAIL PROTECTED]> > List-Id: "Tomcat Developers List" <tomcat-dev.jakarta.apache.org> > > > That would be nice to have tag pooling in 4.x. It was one of those things > that I wanted to do before my day job changed a little. Anyway, a few thoughts: > > Tag pooling as implemented in 3.x is IMHO a good starting point, but generated > code will really benefit if we can handle the more "traditional" optimizing > compiler situations like pulling redundant code (i.e. tag setter methods) out of > loops, etc. Hopefully, with the recent talk of new jasper (very exciting), we > can have a good place to easily integrate such optimizations. > > If you have specific questions about 3.x tag pooling, just let me know... I might > be able to remember some of it. > > -casey > > peter lin wrote: > > > > thanks larry for that information. I will take a look before I jump in. > > > > Larry Isaacs wrote: > > > > > > This was done by Casey Lucas. However, be aware that it comes > > > with a disadvantage in that because of the extra code, it reduces > > > the number of tags you can get on a JSP be for you hit Bug #6088 > > > > > > <http://nagoya.betaversion.org/bugzilla/show_bug.cgi?id=6088> > > > > > > I'm doubtful you can get 100-300 tags on a JSP page in any version > > > of Jasper. Also, check recent posts on this list for a proposed > > > "Jasper2" effort that is underway. See: > > > > Actually, I managed to make a page with about 140 tags that barely > > squeezes under the 64K limit. Under moderate load it runs like a dog. > > When I break it up into smaller pages using action include, it runs much > > better. > > > > > > > > <http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg24054.html> > > > > > > Cheers, > > > Larry > > > > > > > Peter lin > > > > -- > > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
