velocity-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Will Glass-Husain" <>
Subject Re: Doubt about Velocity and performance when using Unicode Encoding
Date Thu, 29 Nov 2007 19:01:50 GMT
Hi Marta,

Typically, performance problems are caused by the cache not being turned
on.  Did you enable the cache for your resource loader?

I haven't seen a problem due to encoding. Would surprise me if the unicode
was the issue.  Maybe there's a difference between the template.merge and
the Velocity.merge calls?

For true scientific comparison, can you run your benchmarks with the new
method call (Velocity.merge) but with the standard encoding?  (Whatever you
used originally with getTemplate).


On Nov 29, 2007 9:16 AM, Marta Gascó Julio <> wrote:

> Hello Velocity users,
> I would like to expose my doubt to you, looking forward for some help from
> you.
> I'm using Velocity as a Template engine in my project and I was happy with
> its performace until I decided use Arabian words in my templates. I changed
> the Encondig to Unicode to make it possible, but since that moment, the time
> needed to Velocity making the "merge" has increased really much.
> I changed my line: lNVTemplate.Merge(lNVContext, lStringWriter);
> For: Velocity.MergeTemplate(lNVTemplate.Name,
> System.Text.Encoding.Unicode.EncodingName, lNVContext, lStringWriter);
> Am I doing any badly? Or is it defect of Velocity? Has any of you
> experienced something like that? Is there any other possibility of merging
> templates with Arabian symbols?
> Thanks in advance for your help.
> Marta.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Forio Business Simulations

Will Glass-Husain

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message