[
https://issues.apache.org/jira/browse/JCR-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Boston updated JCR-2699:
----------------------------
Attachment: DynamicSecurityManager-JCR2699.patch
AccessControlProviderHolder.java
The patch is to my modified version of DefaultSecurityManager, which is a very
close copy of the original.
The AccessControlProviderHolder manages the binding of AccessControlProviders
to threads and provides a cleanup mechanism when threads go. Initial profiling
indicates that with a high volume of thread mortality memory is not leaking.
Neither of these fully solve the problem of thread blocking for highly
concurrent reads, but they do improve the situation a bit.
> 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
> Attachments: AccessControlProviderHolder.java,
> ConcurrentReadTest.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.
