Success!
Just to follow up, I modified TurbineResources.properties and changed all
logging from DEBUG to INFO. I also enabled some more caching as follows:
module.cache=true
services.VelocityService.file.resource.loader.cache = true
This has had quite a noticable affect. Page refreshes are now sub 1 second.
I believe the caching is what did it. The initial compile after restart is
still over 2 minutes... but I think I can live with that. Thanks for all
the suggestions!
Andrew
Werner Punz
<[EMAIL PROTECTED]> To: Jetspeed Users List
<[EMAIL PROTECTED]>
cc:
08/28/02 02:26 PM Subject: Re: jetspeed = slowspeed?
Please respond to
"Jetspeed Users
List"
Just a general note, to the speed, the others have given hints
on how to speed things up already. The mentioned speed in the
beginning of this thread is definitely not normal. I currently
develop into a local jetspeed server and none of my portlets had a
response time
above more than a few miliseconds (tomcat 4.1 increased the speed
which already was good in 3.3.x)
First of all. The first startup takes a little bit of time since
JSPs have to be compiled but after that it should run almost as fast
as a normal JSP page, Velocity is close to non existent in the loading
times. The speed difference between custom JSP pages an jetspeed
portlets/portals is neglegtable from what I saw on my development
system. Kudos to the Velocity/Jetspeed/Turbine developers for that they
did one hell of a job.
--
To unsubscribe, e-mail: <
mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <
mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
