[jira] [Updated] (OAK-4582) Split Segment in a read-only and a read-write implementations

["Francesco Mari (JIRA)" <ji...@apache.org>]

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

Francesco Mari updated OAK-4582:
--------------------------------
    Attachment: benchmark-01.txt
                benchmark-01.png

The first round of benchmarks shows that the changes I made had some kind of impact on the performance of some functionalities, but this impact can be considered negligible. The text file contains the raw data of the benchmarks, the command line executed to produce that data and the exact commit hash of the code base when the benchmarks were run.

> Split Segment in a read-only and a read-write implementations
> -------------------------------------------------------------
>
>                 Key: OAK-4582
>                 URL: https://issues.apache.org/jira/browse/OAK-4582
>             Project: Jackrabbit Oak
>          Issue Type: Technical task
>          Components: segment-tar
>            Reporter: Francesco Mari
>            Assignee: Francesco Mari
>              Labels: technical_debt
>             Fix For: 1.8
>
>         Attachments: benchmark-01.png, benchmark-01.txt
>
>
> {{Segment}} is central to the working of the Segment Store, but it currently serves two purposes:
> # It is a temporary storage location for the currently written segment, waiting to be full and flushed to disk.
> # It is a way to parse serialzed segments read from disk.
> To distinguish these two use cases, I suggest to promote {{Segment}} to the status of interface, and to create two different implementations for a read-only and a read-write segments.



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