You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/16 18:27:51 UTC

[jira] [Resolved] (JCR-3064) Concurrent access performance drop

     [ https://issues.apache.org/jira/browse/JCR-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting resolved JCR-3064.
--------------------------------

       Resolution: Not A Problem
    Fix Version/s:     (was: 2.4)

Confirmed that the performance is back to previous level after switching back to the simple security manager. Thus resolving as Not A Problem.
                
> Concurrent access performance drop
> ----------------------------------
>
>                 Key: JCR-3064
>                 URL: https://issues.apache.org/jira/browse/JCR-3064
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>            Reporter: Jukka Zitting
>            Priority: Blocker
>         Attachments: ConcurrentReadTest-2.3.png, ConcurrentReadTest-2011.png, ConcurrentReadTest.png, ConcurrentReadWriteTest-2.3.png, ConcurrentReadWriteTest-2011.png, ConcurrentReadWriteTest.png, JCR-3064-EntryCollector.patch, visualvm-ConcurrentReadTest-2.2.png, visualvm-ConcurrentReadTest-2.3.png
>
>
> Our performance tests show a pretty bad drop in concurrent access performance (both read and write) in the latest trunk when compared to Jackrabbit 2.2. We need to track down the cause and fix it before the 2.3 release.

--
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