[
https://issues.apache.org/jira/browse/OAK-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16634081#comment-16634081
]
Francesco Mari commented on OAK-7788:
-------------------------------------
[~mduerig], before coming up with this patch I tried to create a {{NodeState}}
and {{NodeBuilder}} implementation to encapsulate this behaviour. As you can
imagine, I failed because of the interdependency between the
{{SegmentNodeState}} and {{SegmentNodeBuilder}}. Given my failed attempt, I
opted for an ugly although minimal solution.
> Measure read rate for the Segment Store
> ---------------------------------------
>
> Key: OAK-7788
> URL: https://issues.apache.org/jira/browse/OAK-7788
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
> Reporter: Francesco Mari
> Assignee: Francesco Mari
> Priority: Major
> Fix For: 1.10
>
> Attachments: OAK-7788-01.patch
>
>
> In order to better understand the behaviour of the Segment Store, we should
> measure its read rate, defined as the amount of API calls performed by the
> user that might trigger a read to the underlying persistence layer.
> The outermost API we can instrument is the NodeState. Calls to this API
> represent a clear intention of the user to read the repository data. A lower
> level API would not carry the same semantics and would be ineffective for
> deducing the intentions of the user.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
