Hi,
I've done some XWiki profiling and it seems that the biggest bottlenecks are
Velocity template evaluating (in XWikiVelocityRenderer) and Lucene Index
Updater thread...
Did you think about using StringResourceLoader (or something similar)
instead of Velocity.evaluate()? I believe caching parsed ASTs rather than
reparsing the same strings everytime could significantly improve overall
performance.
Here you can find some interesting discussion about StringResourceLoader -->
http://www.mail-archive.com/user@velocity.apache.org/msg02135.html
Well, I'd like to give it a try. Do you know any traps/gotchas I should be
aware of?
Kind regards
Lukasz