jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bart van der Schans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3449) Improved performance for concurrent read-only access
Date Mon, 05 Nov 2012 14:12:14 GMT

    [ https://issues.apache.org/jira/browse/JCR-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490647#comment-13490647

Bart van der Schans commented on JCR-3449:

Hi Lars,

When running in these kinds of concurrent session usages performance issues it might be better
to just use a session per thread. That should "fix" the performance. In general JCR sessions
are not designed to be used by multiple threads. The session overhead should be pretty small.

> Improved performance for concurrent read-only access
> ----------------------------------------------------
>                 Key: JCR-3449
>                 URL: https://issues.apache.org/jira/browse/JCR-3449
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>    Affects Versions: 2.2.13, 2.4.3
>            Reporter: Lars Michele
>            Priority: Minor
>         Attachments: jackrabbit-concurrent-read.patch
> This patch relates to JCR-890. The current implementation allows to share a session across
multiple threads reading, but the locking mechanism used makes this use-case slow. The attached
patch uses a ReentrantReadWriteLock for accessing session internals, which allows concurrent
reads be executed concurrently. The only drawback is, that for the "autofix" feature to work
as before one has to instantiate a thread on such cases, because it cannot be executed in
the read-scope of a the session facing such problems.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message