[
https://issues.apache.org/jira/browse/OAK-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488591#comment-13488591
]
Marcel Reutegger commented on OAK-413:
--------------------------------------
AFAICS the problem is not that snapshot() is called. That's OK, as long as it
doesn't create those MutableNodeState overlays unnecessarily (and recursively)
for nodes that are only read. AFAIU this would make the snapshot() call very
quick because it doesn't traverse down the hierarchy.
> TreeLocation.getStatus() cost increases as more content is read below this
> location
> -----------------------------------------------------------------------------------
>
> Key: OAK-413
> URL: https://issues.apache.org/jira/browse/OAK-413
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Affects Versions: 0.5
> Reporter: Marcel Reutegger
> Attachments: OAK-413.patch
>
>
> The more content is read below a given location the more expensive the
> getStatus() becomes on that TreeLocation. There seem to be two issues:
> - Reading creates snapshots in MemoryNodeBuilder depending on how the tree is
> accessed.
> - Cost for comparing states also increases as snapshots are created for
> NodeStates.
> I'll attach a test that shows the described behaviour.
--
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
