Folks, here's a screenshot from JProfiler. This should explain why
our tests are fairly slow...
Simply put; we're not using EhCache, and also we're calling Stripes
ResolverUtil.findImplementations twice per WikiEngine startup. So it
might make sense to move findImplementations() calls into a singleton
or something. But I'm not too sure whether it makes sense considering
restarts - or perhaps restarts should clean away the singleton cache?
(This is after about 700 tests were run; I didn't want to wait until
they had all finished, since it had already taken about two hours with
profiling on...)
Priha can be seen taking quite a lot of time as well, but that's
because it needs to hit the disk all the time. More optimization for
FileProvider is needed, but partly it's also because we're not caching
anything.
/Janne
- Current tests slowdowns analysis Janne Jalkanen
-
