When I switched my projects from JSP to Velocity, I did it more for:
- simplicity of the language (VTL)
- taking away (from web designers) the power to write/execute Java
directly
but if it's fast as well, even better :-)
Bojan
PS. It does take longer to get the first page. Velocity has to start and
all...
Jon Stevens wrote:
>
> Not exactly scientific, but I do trust Rickard to do things correctly...he
> has an existing JSP page for testing and then converted it to
> Velocity...here are the results...
>
> JSP - 240-480ms
> Velocity - 50-70ms
>
> You make the decision.
>
> :-)
>
> -jon
>
> ------ Forwarded Message
> From: Rickard Öberg <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> Date: Mon, 06 Aug 2001 17:41:37 +0200
> To: [EMAIL PROTECTED]
> Cc: Webwork-User <[EMAIL PROTECTED]>
> Subject: Re: Velocity monthlist
>
> Rickard Öberg wrote:
> > Ok guys, this is latest(-ish) Catalina sources. I tried hitting the page
> > a couple of hundred times before checking the time, and it stabilized at
> > scores around 50-70ms. So, that's like, 6 times faster than the same JSP
> > running on Tomcat 3.2. And the VM was direct converted, almost line by
> > line, since the WebWork taglib is very similar to the Velocity
> > directives, so it's a quite fair comparison.
>
> And to make this comparison even more fair, I just tested the JSP page
> on the same Catalina build, and it scored between 240-480ms. So, not
> only is it slower, it is more fluctuating (and I also think I dare say
> that the JSP taglib in WebWork is as optimized as it can be).
>
> Interesting...
>
> /Rickard
>
> --
> Rickard Öberg
> Software Development Specialist
> xlurc - Xpedio Linköping Ubiquitous Research Center
> Author of "Mastering RMI"
> Email: [EMAIL PROTECTED]
>
> ------ End of Forwarded Message
