tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlos Gaston Alvarez" <gast...@tournet.com.ar>
Subject RE: Jasper performance
Date Wed, 16 May 2001 11:29:52 GMT
Have you said a Meg of html !!!
Those are the test cases I need.

Chau,

Gaston


----- Original Message -----
From: <ken.horn@arcordia.com>
To: <tomcat-dev@jakarta.apache.org>
Sent: Tuesday, May 15, 2001 12:41 PM
Subject: Re: Jasper performance



We use Jasper (from a 3.1 build!) in another container. How big is the
change if we wanted to move to the 3.3 version to get the tag pooling. I'm
about to start performance testing our app, and currently the pages are
taking ages to render (we build up to 1Meg of html.. :o), so we'll be
looking at this area soon.

In terms of a quick hit, anybody got opinions / experience of changing the
generation to use an unsynchronized version of StringBuffer, I think this
may show up as a possible easy enhancement.

Ken.





cmanolache@yahoo.com on 15/05/2001 15:22:17

Please respond to tomcat-dev@jakarta.apache.org

To:   tomcat-dev@jakarta.apache.org
cc:    (bcc: Ken X Horn)
Subject:  Re: Jasper performance




> Jasper performance has already been identified as an area needing
> improvement.
>
> Discussions and work on this has already started in the main tomcat
> branch in CVS jakarta-tomcat/proposals/jasper34, but this may be
> moving to the CVS repository jakarta-tomcat-jasper.
>
> This work just started recently, I don't know when it will be ready.

It will take few months - it's not that easy.

We already added tag pooling in tomcat3.3, and that have a significant
effect on performance if you are using tags - but that's just the
beginning.

The first step is to reorganize the code. Then we'll try to make the code
generator more customizable ( probably by using XSLT for some of the
operations ). The real performance enhancement will come when we start
tunning the generated code - there are many ideas around, but we need the
refactoring first.

BTW, jasper will share most of the code for the 1.1 and 1.2 APIs, so all
enhancements will be available in both 3.x and 4.x ( and other containers
as well ).

If you have ideas, code or opinions - please get involved, we need you :-)


Costin



>
> Rickard Öberg wrote:
> >
> > Hi!
> >
> > We are using Tomcat/JBoss and are pleased with the actual
functionality.
> > What is killing us right now is the performance of the code generated
by
> > Jasper, especially when using taglibs in complex ways. The generated
> > code is way too unoptimized.
> >
> > So, if this has not been asked before (in which case a RTFA is ok,
> > although I've looked already), my question is:
> > When will Jasper be rewritten?
> > Are there any such projects underway now?
> > Have there been any discussions about this yet?
> > Am I the only one seeing this problem, or are more people concernced
> > about it?
> >
> > Thanks,
> >   Rickard
> >
> > --
> > Rickard Öberg
> > Software Development Specialist
> > xlurc - Xpedio Linköping Ubiquitous Research Center
> > Author of "Mastering RMI"
> > Email: rickard@xpedio.com
>
>









Mime
View raw message