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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2013/09/23 13:42:02 UTC

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

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

Michael Dürig updated OAK-663:
------------------------------

    Labels: perfomance  (was: )
    
> 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: perfomance
>
> 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