Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: tomcat-dev@jakarta.apache.org
Message-ID: <1916.204.73.215.42.989944046.squirrel@znutar.cortexity.com>
Date: Tue, 15 May 2001 11:27:26 -0500 (CDT)
Subject: Re: Jasper performance
From: "Nick Bauman" <nick@cortexity.com>
To: tomcat-dev@jakarta.apache.org
In-Reply-To: <Pine.LNX.4.21.0105150715020.1178-100000@simona.wyn.org>
References: <Pine.LNX.4.21.0105150715020.1178-100000@simona.wyn.org>
Reply-To: nick@cortexity.com
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

I, for one, would be very interested in making it easy/possible to uncouple
Jasper from the servlet container itself. The question I have is How much of
a scaffolding is required to use Jasper purely as a template engine without
the baggage of the servlet container per se (or at worst, by being able to
call the _jspservice method with a parameters of (HttpServletRequest,
HttpServletResponse) from within an application instead of over the wire
with http).

Is there anyone who has done this already?

> 
>> 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
>> 
>> 


-- 
Nick Bauman
Software Developer
3023 Lynn #22
Minneapolis, MN
55416
Mobile Phone: (612) 810-7406