[jira] [Updated] (OAK-4844) Analyse effects of simplified record ids

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

     [ https://issues.apache.org/jira/browse/OAK-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dürig updated OAK-4844:
-------------------------------
    Attachment: OAK-4844.patch

Attaching [^OAK-4844.patch] which squeezes the size of record ids to 6 bytes. It does so by pretty much the same mechanism we had pre OAK-4631. Just that it is using an integer now as an index into the table of segment references instead of a byte (thus 6 bytes instead of 3). This is to ensure we don't regress on OAK-2896.

[~alex.parvulescu] could you run upgrade with this patch on you test repositories and share the results here so we can compare pre OAK-4631, post OAK-4631 and OAK-4631 with this patch?
[~dulceanu] I had to adjust a test expectation in {{MBeanTests.testClientAndServerEmptyConfig()}}. Please double check. 

[~frm] please review and comment


> Analyse effects of simplified record ids
> ----------------------------------------
>
>                 Key: OAK-4844
>                 URL: https://issues.apache.org/jira/browse/OAK-4844
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segment-tar
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>              Labels: performance
>             Fix For: Segment Tar 0.0.14
>
>         Attachments: OAK-4844.patch
>
>
> OAK-4631 introduced a simplified serialisation for record ids. This causes their footprint on disk to increase from 3 bytes to 18 bytes. OAK-4631 has some initial analysis on the effect this is having on repositories as a whole. 
> I'm opening this issue as a dedicated task to further look into mitigation strategies (if necessary). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)