I've noticed the same. Two reasons: Stripes locating all the classes
(and JSPWiki doing the same for all plugins), and also Priha startup
taking a lot of time due to unoptimized use of XPath when locating
built-in nodes. The latter is fairly easy to optimize - it's just not
been a priority for me (help wanted!). We could also use JNDI in
which case we could skip Priha init.
/Janne
On 15 Feb 2009, at 16:01, Harry Metske wrote:
I have been looking a bit at the performance of our JUnit tests and
summarized it at :
http://www.jspwiki.org/wiki/JUnit%20Test%20performance
In short:
- JUnit tests for 3.0 take 3 times longer than for 2.8
- I like to suggest using attribute forkmode="once" maxmemory="512m"
in the
tests task in build.xml
Any other suggestions are welcome.
Harry
