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

["Michael Dürig (JIRA)" <ji...@apache.org>]

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

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

At [http://svn.apache.org/viewvc?rev=1831089&view=rev] I added the {{RandomAccessTrace}} for collected random access traces. 

> 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
>            Priority: Major
>              Labels: scalability
>             Fix For: 1.10
>
>         Attachments: compaction-time-vs-reposize.m, compaction-time-vs.reposize.png, data00053a.tar-reads.png, offrc.jfr, segment-per-path-compacted-nocache.png, segment-per-path-compacted-nostringcache.png, segment-per-path-compacted.png, segment-per-path.png, segment-reads.png
>
>
> 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)?
> * How good are checkpoints deduplicated? Can we monitor this online?
> * ...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)