[
https://issues.apache.org/jira/browse/OAK-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13920980#comment-13920980
]
Jukka Zitting commented on OAK-1418:
------------------------------------
A few followup changes bring the breakdown of Node.getProperty() to a more
reasonable:
* 40% in Tree.getProperty()
* 21% in RefreshStrategy.needsRefresh()
* 12% in getOakPathOrThrowNotFound()
There's still some room for improvement in needsRefresh() and getOakPath(), it
would be good to have Tree.getProperty() to account for at least half the time
of Node.getProperty().
The numbers on my laptop (Lenowo W530, i7-3840, Windows, Java 1.7.0_40):
{noformat}
Apache Jackrabbit Oak 0.19-SNAPSHOT
# ReadPropertyTest C min 10% 50% 90% max
N
Jackrabbit 1 3 4 4 4 30
15155
Oak-Tar 1 5 5 5 6 28
11461
{noformat}
> 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
> 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)
