Thanks for the answers, I think it's my mystake !
In my velocity.properties file.resource.loader.cache was set to false,
when I set to true, it's OK.
By the way, what is the best velocity.properties configuration ?
here's my production configuration :
# PRODUCTION
file.resource.loader.cache = true
file.resource.loader.modificationCheckInterval = -1
velocimacro.library.autoreload = false
parser.pool.size = 10
Le 12/12/2014 16:04, Boris Partensky a écrit :
Wonder if it's related to "directive.if.tostring.nullcheck" setting,
which defaults to "true". In our case it caused tons of GC tenuring
(leading to pauses, full GC etc) because it calls toString() on every
single object (including collections). I'd look first if performance
hit is due to GC.
On Fri, Dec 12, 2014 at 9:14 AM, Claude Brisson <cla...@renegat.net
<mailto:cla...@renegat.net>> wrote:
That's the first feedback like this we get. If you provide us with
some profiling information, we may help...
Regards,
Claude
On 12/12/2014 14:52, TNO wrote:
Hi,
we try a few month ago to upgrade velocity to 1.7 from 1.4.
Just a replacement in Maven pom.xml.
Then, we measure a lot of treatment before and after and and
what our surprise : it 'is about 10 times slower with velocity
1.7 !
Did I miss something ?
Cherrs, Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org
<mailto:user-unsubscr...@velocity.apache.org>
For additional commands, e-mail: user-h...@velocity.apache.org
<mailto:user-h...@velocity.apache.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org
<mailto:user-unsubscr...@velocity.apache.org>
For additional commands, e-mail: user-h...@velocity.apache.org
<mailto:user-h...@velocity.apache.org>
