jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-7788) Measure read rate for the Segment Store
Date Mon, 01 Oct 2018 14:22:00 GMT

    [ https://issues.apache.org/jira/browse/OAK-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16634087#comment-16634087

Michael Dürig commented on OAK-7788:

{quote}encapsulate this behaviour
Ouch, I can imaging this is even worse, {{SegmentNodeState.builder}} being the worst offender.
In hindsight, this method is probably the single biggest mistake in the node store API.

> 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

View raw message