[
https://issues.apache.org/jira/browse/OAK-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924018#comment-13924018
]
Jukka Zitting commented on OAK-1418:
------------------------------------
For completeness, here's also the updated profiling breakdown of the time spent
in Node.getProperty():
* 62% in Tree.getProperty(), including 15% in SegmentNodeState.getProperty()
* 20% in getOakPathOrThrowNotFound()
It should be noted that at this level the profiling results are already
somewhat inaccurate as the component calls take only fractions of microseconds
and the locations of profiling samples may be heavily affected by JIT
compilation. See http://www-plan.cs.colorado.edu/klipto/mytkowicz-pldi10.pdf
for more background.
> Read performance regression
> ---------------------------
>
> Key: OAK-1418
> URL: https://issues.apache.org/jira/browse/OAK-1418
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Environment: Oak 0.17-SNAPSHOT
> Reporter: Marcel Reutegger
> Assignee: Alex Parvulescu
> Fix For: 0.19
>
> Attachments: ReadPropertyTest.png
>
>
> A recent benchmark run of ReadPropertyTest shows a performance regression.
> The most recent run (206) was executed last night and the previous one (200)
> is from Feb 6th.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
