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/12 16:38:51 UTC
[jira] [Resolved] (OAK-1015) Optimise path parsing
[ https://issues.apache.org/jira/browse/OAK-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dürig resolved OAK-1015.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.9
> Optimise path parsing
> ---------------------
>
> Key: OAK-1015
> URL: https://issues.apache.org/jira/browse/OAK-1015
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: core
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Fix For: 0.9
>
>
> As Jukka [mentioned | https://issues.apache.org/jira/browse/OAK-978?focusedCommentId=13751242&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13751242] on OAK-978, is often on the critical path and the changes done there had a bad impact on performance:
> {code}
> Apache Jackrabbit Oak
> # ReadPropertyTest min 10% 50% 90% max N
> Jackrabbit 4 5 5 6 14 11287
> Oak-Tar 14 15 16 16 27 3855
> {code}
> Until we are able to come up with a better solution that separates parsing from name mapping, I suggest to use the following heuristic to shortcut path parsing: shortcut iff the JCR path does not start with a dot, does not contain any of {}[]/ and if it contains a colon the session does not have local re-mappings.
--
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