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

ASF GitHub Bot commented on IGNITE-7182:
----------------------------------------

GitHub user dspavlov opened a pull request:

    https://github.com/apache/ignite/pull/3244

    IGNITE-7182: throttle only changes

    Part of implementation changes throttling policy

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite 
ignite-7182-throttle-only

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/3244.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3244
    
----
commit dd8a7ac47df1dc401e5a98dc21f9a0988fb50b0f
Author: dpavlov <[email protected]>
Date:   2017-12-01T16:47:45Z

    GG-13117: PDS compatibility test flaky failure: debug code added

commit 6c7b4fb24542672944220dca94efffa94a969ee2
Author: dspavlov <[email protected]>
Date:   2017-12-16T07:49:42Z

    IGNITE-7182: Throttle only changes, fixes too aggressive throttling at CP 
begin

----


> Slow sorting of pages collection on checkpoint begin can cause zero dropdown 
> even with throttling enabled
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-7182
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7182
>             Project: Ignite
>          Issue Type: Improvement
>          Components: persistence
>    Affects Versions: 2.3
>            Reporter: Ivan Rakov
>            Assignee: Dmitriy Pavlov
>             Fix For: 2.4
>
>
> Tests show that GridCacheDatabaseSharedManager#splitAndSortCpPagesIfNeeded 
> call can last several seconds on nodes with big amount of memory (>10GB). We 
> should optimize sorting algorithm, possibly making it multithreaded.
> Another option to make pages write throttling more smooth is to get rid of 
> this heuristic:
> {noformat}
>                 // Starting with 0.05 to avoid throttle right after 
> checkpoint start
>                 // 7/12 is maximum ratio of dirty pages
>                 dirtyRatioThreshold = (dirtyRatioThreshold * 0.95 + 0.05) * 7 
> / 12;
> {noformat}
> We should replace "magic" lower bound 0.05 * 7 / 12 with the real percentage 
> of dirty pages at the moment of 
> GridCacheDatabaseSharedManager.Checkpointer#markCheckpointBegin call return.



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

Reply via email to