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

["Jukka Zitting (JIRA)" <ji...@apache.org>]

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

Jukka Zitting resolved OAK-663.
-------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 0.12)
                   0.11

Resolving this as fixed as the key problems have already been resolved. For example the property access case that originally triggered this issue is already covered:

{noformat}
# ReadPropertyTest                 C     min     10%     50%     90%     max       N
Jackrabbit                         1       3       4       4       4      90   15074
Oak-Tar                            1       4       4       4       5      16   14199
{noformat}

Any remaining and/or further optimizations should be tracked in more specific issues.

> 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
>              Labels: performance
>             Fix For: 0.11
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)