You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2013/07/02 18:19:19 UTC

[jira] [Commented] (OAK-663) oak-jcr performance optimization

    [ https://issues.apache.org/jira/browse/OAK-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697932#comment-13697932 ] 

Jukka Zitting commented on OAK-663:
-----------------------------------

In http://svn.apache.org/r1498995 I adjusted {{ItemImpl}} to only check for item staleness after some transient or persisted operation has been made (tracked by an update counter in {{SessionDelegate}}). This avoids the need for repeated staleness checks even in read-only sessions that are never refreshed, thus boosting performance for many common cases.
                
> oak-jcr performance optimization
> --------------------------------
>
>                 Key: OAK-663
>                 URL: https://issues.apache.org/jira/browse/OAK-663
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: jcr
>            Reporter: Jukka Zitting
>            Priority: Critical
>
> Currently oak-jcr does a lot of unnecessary work for various reasons. This is a major drag on performance.
> For example, a getString() call on an already acquired PropertyImpl instance (with no refresh() or other operations in between) requires 12 (!) NodeBuilder.getProperty() calls to access that same property state over and over again.

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