Re: Performance tuning/improvements

It may also be that since jsp's are compiled, static contents become
hard-coded string literals where velocity can only cache them as some
kind of variable type (string, stringbuffer).
jim
-- 
/**
 * Jim McLaughlin
 * Senior Software Engineer
 * Stonewater Controls
 * 847.864.1060 x107
 */


On Fri, Nov 22, 2002 at 08:55:26AM -0800 or thereabouts, David You wrote:
> Resin put lots of effort on performance at the begining. For example, They
> use it's own unsynchronized CharacterBuffer? instead of StringBuffer which
> is synchronized.
> 
> David
> 
> 
> -----Original Message-----
> From: Gabriel Sidler [mailto:sidler@xxxxxxxxxx]
> Sent: Friday, November 22, 2002 7:56 AM
> To: Velocity Users List
> Subject: Re: Performance tuning/improvements
> 
> 
> Since we are talking about performance...
> 
> I noticed that the JSP Servlet of Resin pumps out simple
> templates about 2 to 3 times as fast as the Velocity
> servlet under the same circumstances.
> 
> By 'simple template' I mean a template that is mostly static.
> If the template is very dynamic, the performance advantage
> of Resin/JSP is smaller.
> 
> They must be doing something very smart about moving the
> bytes around. Does anyone have an idea how they can achieve
> this huge performance advantage with static templates?
> 
> Gabe
> 
> 
> 
> 
> 
> --
> Gabriel Sidler
> Software Engineer, Eivycom GmbH, Zurich, Switzerland
> 
> 
> --
> To unsubscribe, e-mail:
> <mailto:velocity-user-unsubscribe@xxxxxxxxxxxxxxxxxx>
> For additional commands, e-mail:
> <mailto:velocity-user-help@xxxxxxxxxxxxxxxxxx>
> 
> --
> To unsubscribe, e-mail:   
> <mailto:velocity-user-unsubscribe@xxxxxxxxxxxxxxxxxx>
> For additional commands, e-mail: 
> <mailto:velocity-user-help@xxxxxxxxxxxxxxxxxx>