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/11/02 03:12:17 UTC
[jira] [Commented] (OAK-1015) Optimise path parsing
[ https://issues.apache.org/jira/browse/OAK-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811843#comment-13811843 ]
Jukka Zitting commented on OAK-1015:
------------------------------------
As a followup on this, I further improved the heuristics in revision 1538131. The result:
{noformat}
Apache Jackrabbit Oak 0.11-SNAPSHOT
# ReadPropertyTest C min 10% 50% 90% max N
Jackrabbit 1 3 4 4 4 63 15116
Oak-Tar (before) 1 4 5 5 5 34 11937
Oak-Tar (after) 1 3 3 4 4 29 15240
{noformat}
> 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
> Labels: performance
> 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 was sent by Atlassian JIRA
(v6.1#6144)