[
https://issues.apache.org/jira/browse/JCR-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463150
]
Jukka Zitting commented on JCR-688:
-----------------------------------
Committed version 3 of the NameResolver classes in revision 494219. The
committed classes have some minor differences to the above proposals, most
notably:
a) ParsingNameResolver was further optimized and is now most likely the fastest
validating JCR name parser there is.
b) CachingNameResolver now caches both parsed and formatted names, as
benchmarking showed noticeable gain from doing so.
c) CachingNameResolver was simplified so that only a single synchronized method
is required for controlling concurrency.
> Improve name resolution
> -----------------------
>
> Key: JCR-688
> URL: https://issues.apache.org/jira/browse/JCR-688
> Project: Jackrabbit
> Issue Type: Improvement
> Components: core
> Reporter: Jukka Zitting
> Assigned To: Jukka Zitting
> Priority: Minor
> Fix For: 1.3
>
> Attachments: JCR-688.LocalCache.patch, JCR-688.NameResolver.patch,
> JCR-688.NameResolver.v2.patch
>
>
> As discussed in JCR-685, the current CachingNamespaceResolver class contains
> excessive synchronization causing monitor contention that reduces performance.
> In JCR-685 there's a proposed patch that replaces synchronization with a
> read-write lock that would allow concurrent read access to the name cache.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
