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 "Andrei Dulceanu (JIRA)" <ji...@apache.org> on 2016/11/03 14:32:58 UTC
[jira] [Updated] (OAK-5058) Improve GC estimation strategy based on
both absolute size and relative percentage
[ https://issues.apache.org/jira/browse/OAK-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Dulceanu updated OAK-5058:
---------------------------------
Summary: Improve GC estimation strategy based on both absolute size and relative percentage (was: Improve GC running strategy based on both absolute size and relative percentage)
> Improve GC estimation strategy based on both absolute size and relative percentage
> ----------------------------------------------------------------------------------
>
> Key: OAK-5058
> URL: https://issues.apache.org/jira/browse/OAK-5058
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
> Affects Versions: 1.5.12
> Reporter: Andrei Dulceanu
> Assignee: Andrei Dulceanu
> Priority: Minor
> Fix For: 1.5.14
>
>
> A better way of deciding whether GC should run or not might be by looking at the numbers computed in {{SizeDeltaGcEstimation}} from both an absolute size and relative percentage point of view. For example it would make sense to run compaction only if both criteria are met: "run if there is > 50% increase or more than 10GB".
> Since the absolute threshold is already implemented (see {{SegmentGCOptions.SIZE_DELTA_ESTIMATION_DEFAULT}}), it would be nice to add also something like {{SegmentGCOptions.SIZE_PERCENTAGE_ESTIMATION_DEFAULT}} and use it in taking the decision.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)