You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Stefan Egli (Jira)" <ji...@apache.org> on 2024/04/15 17:35:00 UTC

[jira] [Commented] (OAK-10764) gap orphans improvement : only lookup greatest existing ancestor, then cache

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

Stefan Egli commented on OAK-10764:
-----------------------------------

PR created at https://github.com/apache/jackrabbit-oak/pull/1420

> gap orphans improvement : only lookup greatest existing ancestor, then cache
> ----------------------------------------------------------------------------
>
>                 Key: OAK-10764
>                 URL: https://issues.apache.org/jira/browse/OAK-10764
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: documentmk
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>            Priority: Major
>              Labels: DetailedGC
>
> Follow-up of OAK-10761 : to further improve gap vs non-gap orphan type detection, lookup only the direct child of the greatest existing ancestor, then cache that result. Upon further type detection, use that cache to start with. That eliminates the tree traversal, plus using the cache should further limit the number of lookups in the first place. The cache can be small (eg 64) and assuming paths aren't excessive (say max 10k) the resulting memory usage would still be small (eg 64k characters).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)