[jira] [Resolved] (OAK-3070) Use a lower bound in VersionGC query to avoid checking unmodified once deleted docs

["Marcel Reutegger (JIRA)" <ji...@apache.org>]

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

Marcel Reutegger resolved OAK-3070.
-----------------------------------
       Resolution: Fixed
         Assignee: Marcel Reutegger  (was: Vikas Saurabh)
    Fix Version/s: 1.8
                   1.7.0

Applied the most recent patch to trunk: http://svn.apache.org/r1786145

> Use a lower bound in VersionGC query to avoid checking unmodified once deleted docs
> -----------------------------------------------------------------------------------
>
>                 Key: OAK-3070
>                 URL: https://issues.apache.org/jira/browse/OAK-3070
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mongomk, rdbmk
>            Reporter: Chetan Mehrotra
>            Assignee: Marcel Reutegger
>              Labels: performance
>             Fix For: 1.7.0, 1.8
>
>         Attachments: OAK-3070-2.patch, OAK-3070-3.patch, OAK-3070.patch, OAK-3070-updated.patch, OAK-3070-updated.patch
>
>
> As part of OAK-3062 [~mreutegg] suggested
> {quote}
> As a further optimization we could also limit the lower bound of the _modified
> range. The revision GC does not need to check documents with a _deletedOnce
> again if they were not modified after the last successful GC run. If they
> didn't change and were considered existing during the last run, then they
> must still exist in the current GC run. To make this work, we'd need to
> track the last successful revision GC run. 
> {quote}
> Lowest last validated _modified can be possibly saved in settings collection and reused for next run



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