jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-2699) Improve read/write concurrency
Date Tue, 05 Oct 2010 10:08:33 GMT

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

Jukka Zitting resolved JCR-2699.

       Resolution: Fixed
    Fix Version/s: 2.2.0

Looking at this from the other way, the total throughput of the 20 background readers also
improved about 20% (9.2m reads per minute vs. 7.6m in Jackrabbit 2.1).

Resolving as fixed, as I think we're about done here. See JCR-2573 and JCR-2762 for some further
areas where performance could be improved.

> Improve read/write concurrency
> ------------------------------
>                 Key: JCR-2699
>                 URL: https://issues.apache.org/jira/browse/JCR-2699
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 2.2.0
>         Attachments: AccessControlProviderHolder.java, ConcurrentReadTest.png, ConcurrentReadTest.png,
ConcurrentReadWriteTest.png, DynamicSecurityManager-JCR2699.patch
> I'd like to set up a few performance tests to help identify our worst bottlenecks for
various kinds of concurrent read-only and read-write access patterns.
> Once identified, I'm hoping to fix at least some of those bottlenecks.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message