jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francesco Mari (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-4122) Replace the commit semaphore in the segment node store with a scheduler
Date Fri, 22 Jul 2016 14:11:23 GMT

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

Francesco Mari updated OAK-4122:
--------------------------------
    Fix Version/s:     (was: Segment Tar 0.0.6)
                   Segment Tar 0.0.8

> Replace the commit semaphore in the segment node store with a scheduler
> -----------------------------------------------------------------------
>
>                 Key: OAK-4122
>                 URL: https://issues.apache.org/jira/browse/OAK-4122
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segment-tar
>            Reporter: Michael Dürig
>            Assignee: Francesco Mari
>              Labels: performance, scalability, throughput
>             Fix For: 1.6, Segment Tar 0.0.8
>
>
> {{SegmentNodeStore}} currently uses a semaphore to coordinate concurrent commits thus
relying on the scheduling algorithm of that implementation and ultimately of the JVM for in
what order commits are processed. 
> I think it would be beneficial to replace that semaphore with an explicit queue of pending
commit. This would allow us to implement a proper scheduler optimising for e.g. minimal system
load, maximal throughput or minimal latency etc. A scheduler could e.g. give precedence to
big commits and order commits along the order of its base revisions, which would decrease
the amount of work to be done in rebasing. 



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

Mime
View raw message