You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Arun Katkere <ka...@praja.com> on 2000/10/24 03:40:21 UTC

"Modern" compilation

While trying to figure out why exactly is Jasper page loading dog slow
(initial compilation is very slow, most time spent in Zip file read, and
page load is slow because of secure session id initialization), I noticed
that Tomcat still uses "classic" javac (sun.tools.javac.Main) instead of
"modern" javac (com.sun.tools.javac.Main) even in JDK 1.3 context. 

Is there plans to support this compiler (which is much faster)? Does anyone
have a patch/plugin we can use?

While trying to write a compiler plugin myself, I realized there is no way
to force the modern compiler to write to my stream instead of
System.out/err. Perhaps this is the reason why modern compiler is not
supported??

Also, use of any compiler plugin other than the standard SunJavaCompiler is
next to impossible since the JSP engine does not read web.xml in
$TOMCAT_HOME/conf. So, we are left with two unfriendly choices. Patch tomcat
code or insert Tomcat specific code into each web.xml. Is there plans to
move JSP compiler plugin specification to server.xml?

Great software, but it is not easy to convince that to folks used to near
instantaneous page compilation/load times of JServ/GNUJSP/jikes combo that
Tomcat is the greatest thing out there when they sit waiting for 30-45
seconds waiting for page to compile (or even just load!!). We are not
talking about bottlenecks in outside code. It is the same with Tomcat sample
JSPs.

-arun

Re: "Modern" compilation

Posted by Ted Husted <ne...@husted.com>.
On 10/23/2000 at 6:40 PM Arun Katkere wrote:
> Great software, but it is not easy to convince that to folks used to
near instantaneous page compilation/load times of JServ/GNUJSP/jikes
combo that Tomcat is the greatest thing out there when they sit waiting
for 30-45 seconds waiting for page to compile (or even just load!!). We
are not talking about bottlenecks in outside code. It is the same with
Tomcat sample
JSPs.

There must be something wrong with your installation. I've tested
Tomcat on multiple platforms, and have never seen a percetible
difference between Tomcat and a JServ/GNUJSP/jikes combo. Waiting 30-35
seconds on the sample JSPs is just plain wrong.

-Ted.


Re: "Modern" compilation

Posted by Patrick Beard <be...@netscape.com>.
At 6:40 PM -0700 10/23/2000, Arun Katkere wrote:
>While trying to figure out why exactly is Jasper page loading dog slow
>(initial compilation is very slow, most time spent in Zip file read, and
>page load is slow because of secure session id initialization), I noticed
>that Tomcat still uses "classic" javac (sun.tools.javac.Main) instead of
>"modern" javac (com.sun.tools.javac.Main) even in JDK 1.3 context.

I've seen serious performance problems with the current 3.3 
development version, but the 3.1 release is quite snappy, so I really 
doubt this is a compiler performance problem.

>Great software, but it is not easy to convince that to folks used to near
>instantaneous page compilation/load times of JServ/GNUJSP/jikes combo that
>Tomcat is the greatest thing out there when they sit waiting for 30-45
>seconds waiting for page to compile (or even just load!!). We are not
>talking about bottlenecks in outside code. It is the same with Tomcat sample
>JSPs.

Which version of Tomcat are you running against? On my Powerbook 
G3/500, I get near instantaneous page loads using Tomcat 3.1.

- Patrick
-- 

// Patrick C. Beard
// Java Runtime Enthusiast -- "Will invoke interfaces for food."
// mailto:beard@netscape.com

Re: "Modern" compilation

Posted by casper mdb <ca...@mdb.ku.dk>.
Arun Katkere  <ka...@praja.com> wrote
> ....
> Great software, but it is not easy to convince that to folks used to near
> instantaneous page compilation/load times of JServ/GNUJSP/jikes combo that
> Tomcat is the greatest thing out there when they sit waiting for 30-45
> seconds waiting for page to compile (or even just load!!). We are not
> talking about bottlenecks in outside code. It is the same with Tomcat sample
> JSPs.

I have never been waiting 30-45 seconds with Tomcat, not even on my experimentel Linuxbox - a Pentium 100MHz with 64 MB. It is more like 5-10 seconds. I tried Rasin with Jikes last night, wich compiled new jsp-pages so fast (< 1s), that I thougth I had made a mistake updating my files. 
But overall I really really like Tomcat. So keep up the good work. 

-Casper