Dan Brown wrote:
> 
> I have built the newapp application and turned on all cacheing to get a
> good feel on the speed of the application.  Overall I am impressed, but
> the initial load of the Login page and the Index page after a successful
> login is very slow on the order of 35 sec for the login page,  20 sec
> for the Index page.  Without knowing the details of the application, I
> was wondering what facilities are available in turbine that can be
> leveraged to preload pages or get initial resources prior to the first
> hit to the site?

If you are using the latest tdk than the reason appears to be
catalina. When I switched versions of catalina, CVS for the b5
release the speed seemed to drop off the deep end. I'm trying
to track down the problem but I haven't setup a profiler yet.

I was thinking of trying Resin in the TDK to try and pick up
the speed a bit. Catalina is first and foremost trying to stick
to the servlet spec, that is the first priority. The optimization
will come later, but I admit it's kind of slow. Or it sure feels
like it anyway. Jon is finding the same thing with Scarab slowing
down and he thinks it's something in Turbine. I think it's something
in Catalina but I'm just guessing really.

I think this because I used an identical build process to make
a TDK with two different versions of Catalina b2 and b5 and the
speed dropped off considerably when using b5. We'll find it
eventually.

You can always drop the webapp created with the TDK into another
servlet container if you need a performance boost.

> Thanks,
> 
> - Dan
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]

http://jakarta.apache.org/velocity
http://jakarta.apache.org/turbine
http://jakarta.apache.org/commons
http://tambora.zenplex.org

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to