Re: Performance tuning/improvements

Cool. Good to hear that.
I did a very elementary benchmarking to see whether it performs better than
the homegrown solution (No doubt it does with caching).
I found that it was able to process approx 1500 templates in one second.
That probably translates to the figure that you were talking.
The templates I tried out in the test were pretty much basic with simple
variable replacements and one #for control loop.

The reason I am looking for performance improvements is that the application
does several other things which are much more CPU intensive than
velocity. As it is velocity seems to satify my requirements. Was just
wondering if there is any scope for improvements if the need arises ?.

regards
Ramesh

----- Original Message -----
From: "Peter Romianowski" <megapero@xxxxxx>
To: "'Velocity Users List'" <velocity-user@xxxxxxxxxxxxxxxxxx>
Sent: Friday, November 22, 2002 8:33 PM
Subject: RE: Performance tuning/improvements


>   I implemented a "mail rendering" engine based on velocity a
> while ago. With quite sophisticated velocity-templates and
> a lot of other procession stuff I managed to generate over
> a million mails / hour (including all the javax.mail - stuff,
> so, a "ready-to-send" email!) on a P4 2GHz desktop. And that was
> *without* caching. Have you done any performance test by now?
>
>   Nevertheless, looking for performance improvements is never
> wrong! :)
>
> Peter
>
> > -----Original Message-----
> > From: Mailing Lists Account [mailto:mlists@xxxxxxxxxx]
> > Sent: Friday, November 22, 2002 9:50 AM
> > To: Velocity Users List
> > Subject: Re: Performance tuning/improvements
> >
> >
> > Thanks for Java1.4 tip. I didn't know that.
> > Network delay is beyond the tools control. However,
> > processing the email template before sending out is certainly
> > something that I can do and that is where I plan to use and
> > optimize velocity use (if possible) .
> >
> > regards
> > Ramesh
> >
> > ----- Original Message -----
> > From: "David You" <David.You@xxxxxxx>
> > To: "'Velocity Users List'" <velocity-user@xxxxxxxxxxxxxxxxxx>
> > Sent: Friday, November 22, 2002 3:06 AM
> > Subject: RE: Performance tuning/improvements
> >
> >
> > > Use Java 1.4, the Reflection is supposed to be 50 times
> > more faster?
> > > Anyway, I think most time your program spend are probably on the
> > > network
> > to
> > > get the emails from the email server.
> > >
> > > David
> > >
> > >
> > > -----Original Message-----
> > > From: Mailing Lists Account [mailto:mlists@xxxxxxxxxx]
> > > Sent: Thursday, November 21, 2002 12:50 PM
> > > To: velocity-user@xxxxxxxxxxxxxxxxxx
> > > Subject: Performance tuning/improvements
> > >
> > >
> > > Hi,
> > >
> > > I am planning to deploy Velocity(v1.3) in a stand-alone Java
> > > application
> > to
> > > process email templates.
> > > A little benchmark test of my own shows that Velocity(with caching
> > enabled)
> > > outperforms the existing homegrown solution.
> > >
> > > 1) Since the number of emails to be processed are in
> > thousands/hour,
> > > was wondering if there is any scope for performance improvments ?
> > >
> > > 2) Especially w.r.t reflection, can something be done if
> > the type of
> > > the objects in the context is known and fixed for a given template ?
> > >
> > > 3) Any precautions that I need to take w.r.t memory usage ?
> > >
> > >
> > > thanks
> > > Ramesh
> > >
> > >
> > >
> > > --
> > > 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>
> > >
> > >
> >
> >
> > --
> > 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>
>
>