jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Created] (JCR-3360) Performance degradation in concurrent performance tests due to list of open sessions
Date Wed, 27 Jun 2012 12:26:44 GMT
angela created JCR-3360:
---------------------------

             Summary: Performance degradation in concurrent performance tests due to list
of open sessions
                 Key: JCR-3360
                 URL: https://issues.apache.org/jira/browse/JCR-3360
             Project: Jackrabbit Content Repository
          Issue Type: Bug
          Components: test
            Reporter: angela


julian and myself found an oddity while looking at the concurrent read tests: while running
ConcurrentReadAccessControlledTreeTest we experienced that performance dropped during the
multiple executions of the runTest method.

this behavior occurred both with admin and anonymous session and irrespective of the ac patches
applied.  the test code showing the problem was:

protected void runTest() throws Exception {
        Session testSession = loginReader(); // keeps the session in a list for logout in
teardown
        RandomRead randomRead = new RandomRead(testSession, true);
        randomRead.run();
 }

surprisingly the performance drop was also present if we added testSession.logout right after
the
run method.

the performance drop disappeared in the following cases:

protected void runTest() throws Exception {
        Session testSession = getRepository().login();
        RandomRead randomRead = new RandomRead(testSession, true);
        randomRead.run();
        testSession.logout(); // this one is optional and didn't have an positive effect
 }

the original test code was very similar to the other concurrent performance tests. with those
figures at hand, i would make sense to fix the performance tests in general... and maybe we
should
also look at Session.logout (but that's definitely a different issue).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message