You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Francesco Mari (JIRA)" <ji...@apache.org> on 2018/09/28 11:58:00 UTC

[jira] [Commented] (OAK-7788) Measure read rate for the Segment Store

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

Francesco Mari commented on OAK-7788:
-------------------------------------

The first version of the patch register a new meter {{oak.segment.reads}} with the {{StatisticsProvider}}. The meter is incremented every time a request to read some piece of content is received. [~mduerig], [~dulceanu], can you review?

> 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-7755-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)