jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-4732) (Slightly) prioritise reads over writes
Date Thu, 23 Mar 2017 09:16:41 GMT

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

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

[~dulceanu], I think such an approach should be evaluated and implemented as part of a scheduler
once we have OAK-4122.



> (Slightly) prioritise reads over writes 
> ----------------------------------------
>
>                 Key: OAK-4732
>                 URL: https://issues.apache.org/jira/browse/OAK-4732
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segment-tar
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>            Priority: Minor
>              Labels: Performance, scalability
>             Fix For: 1.8
>
>
> When fetching the current root from the {{SegmentNodeStore}} an older revision will be
returned when a commit is being processed concurrently. I think it would make sense to wait
for a short time in this case increasing the chance of returning an up to date state. The
idea is that this would lower the rebasing work that need to be done later on should the returned
root be used for further modifications. 
> An interesting value for the wait time is to use  the median (or more general a percentile)
of the commit time of the last say 1000 commits. This would mean that (for the median) we
have a 50% chance of getting up to date date. For a 90% percentile we would have longer wait
times but then a 90% chance of getting up to date date. 



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

Mime
View raw message