[jira] [Updated] (OAK-6822) RevisionGC: measure timeToDleteSplitDocs separately

["Julian Reschke (JIRA)" <ji...@apache.org>]

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

Julian Reschke updated OAK-6822:
--------------------------------
    Attachment: OAK-6822.diff

Proposed patch.

Sample output:
{noformat}
VersionGCStats{ignoredGCDueToCheckPoint=false, canceled=false, deletedDocGCCount=102102 (of which leaf: 102000), updateResurrectedGCCount=0, splitDocGCCount=2, intermediateSplitDocGCCount=0, iterationCount=2, timeActive=7.802 s, timeToCollectDeletedDocs=1752 ms, timeToCheckDeletedDocs=260.1 ms, timeToSortDocIds=534.0 us, timeTakenToUpdateResurrectedDocs=18.00 us, timeTakenToDeleteDeletedDocs=5.605 s, timeTakenToCollectAndDeleteSplitDocs=120.7 ms (of which 4.519 ms deleting)}
{noformat}

(where the "(of which ... deleting)" would only be included when the separate timer actually got invoked)


> RevisionGC: measure timeToDleteSplitDocs separately
> ---------------------------------------------------
>
>                 Key: OAK-6822
>                 URL: https://issues.apache.org/jira/browse/OAK-6822
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: documentmk
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>             Fix For: 1.8
>
>         Attachments: OAK-6822.diff
>
>
> ...where we need to deal with the Mongo case where collecting and deleting happens in a single call and thus can't be measured separately.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)