christoph and thomas are both right. svn r471800 caused a serious performance degradation. the maven test suite took approx. 50% longer, specific test cases suffered even more, e.g.:
- org.apache.jackrabbit.test.api.TestAl:; +170% - org.apache.jackrabbit.core.TestAll: +300% for the time being i teverted the changes from r471800. thomas already identified the issue, he'll post a revised patch. cheers stefan On 11/10/06, Thomas Mueller <[EMAIL PROTECTED]> wrote:
Hi, The reason could be the CacheManager, see http://issues.apache.org/jira/browse/JCR-619 Since then, I have posted a new version, see http://issues.apache.org/jira/browse/JCR-625 This change is not yet in the trunk. (The CacheManager was introduced to solve OutOfMemory problems). Thomas On 11/10/06, Christoph Kiehl <[EMAIL PROTECTED]> wrote: > Hi, > > we are experiencing a noticeable to massive performance degradation in > jackrabbit-core. Even the jackrabbit-core unit tests take almost twice as long > as before. The change apparently happened between 2006-11-01 and 2006-11-09. Has > anyone an idea which one of the latest commits might cause this behaviour? > > Cheers, > Christoph > >
