jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davide Giannella (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (OAK-4732) (Slightly) prioritise reads over writes
Date Mon, 24 Jul 2017 13:17:06 GMT

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

Davide Giannella closed OAK-4732.

Bulk close for 1.7.4

> (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: Andrei Dulceanu
>            Priority: Minor
>              Labels: Performance, scalability
>             Fix For: 1.8, 1.7.4
>         Attachments: OAK-4732.patch
> 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

View raw message