With respect to Velocity configuration optimization, every time I refresh the view, it will call “Utils.parseTemplate” methods, but the parsing process seems to have a significant impact on performance. Can I configure the cache of Velocity ？ How ？
If anyone can help me
With Velocity 1.7, caching does more bad than good because of the way #macros are handled and the fact that we use them a bit everywhere in XWiki. The good news is that it’s been greatly improved in Velocity 2.x and we plan to upgrade in XWiki 11.4 and start playing with caching of *.vm templates and {{velocity}} macros.