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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2017/02/14 15:21:41 UTC

[jira] [Commented] (OAK-5655) TarMK: Analyse locality of reference

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

Michael Dürig commented on OAK-5655:
------------------------------------

See [my comment|https://issues.apache.org/jira/browse/OAK-5469?focusedCommentId=15860282&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15860282] on OAK-5469 regarding the tooling I'm working on for creating incidence plots of a repository.

> TarMK: Analyse locality of reference 
> -------------------------------------
>
>                 Key: OAK-5655
>                 URL: https://issues.apache.org/jira/browse/OAK-5655
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: segment-tar
>            Reporter: Michael Dürig
>              Labels: scalability
>             Fix For: 1.8
>
>
> We need to better understand the locality aspects of content stored in TarMK: 
> * How is related content spread over segments?
> * What content do we consider related? 
> * How does locality of related content develop over time when changes are applied?
> * What changes do we consider typical?
> * What is the impact of compaction on locality? 
> * What is the impact of the deduplication caches on locality (during normal operation and during compaction)?
> * ...



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)