Ted:
I didn't mean *after* the page is loaded. Initial page load is
slower because of the reasons I outlined (classic compiler is the default
and using jikes is not an option because editing webapp web.xmls to put
Jasper specific code is not an option, and even after compilation initial
page load takes a long time because of some session id initialization).
This is with plain vanilla Linux and Windows NT with JDK 1.3.0. On Linux,
this is with Tomcat rpm, which I assume does the right thing. And we are
talking about reasonably powered workstations (Pentium III 500, 256MB RAM).
If you have somehow managed to work around these problems, as it appears you
have, please let me know how.
-arun
ps: Guys, am I the only one seeing slow initial page loads with or without
compilation?
> -----Original Message-----
> From: Ted Husted [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 24, 2000 2:03 AM
> To: TomCat Developers List
> Subject: Re: "Modern" compilation
>
>
> 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.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
