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

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

GitHub user alamar opened a pull request:

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

    IGNITE-7489 Factor total allocated pages in data region's fillFactor.

    … add test.

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

    $ git pull https://github.com/gridgain/apache-ignite ignite-7489

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

    https://github.com/apache/ignite/pull/3463.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 #3463
    
----
commit aa35af86b3f06257add6d5a8b1e3098e721729d0
Author: Ilya Kasnacheev <ilya.kasnacheev@...>
Date:   2018-02-01T13:45:12Z

    IGNITE-7489 Factor total allocated pages in data region's fillFactor, add 
test.

----


> Weird FillFactor metric fluctuation.
> ------------------------------------
>
>                 Key: IGNITE-7489
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7489
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.1, 2.2, 2.3
>            Reporter: Andrew Mashenkov
>            Assignee: Ilya Kasnacheev
>            Priority: Major
>         Attachments: FillFactorTest.java
>
>
> For now there is no way to get Used\FreeMemory for region in bytes. 
> MemoryMetrics.getPagesFillFactor() javadoc says that the method return the 
> percentage of space that is still free and can be filled in.
> So, I'd think used memory can be calculated as 
> PhysicalMemoryPages*PageSize*FillFactor.
> I've tried to use this, but found weir thing.
>  
> PFA a repro.
> There is 2 node grid with no persistence configure. Topology is stable.
> Cache is populated with unique keys (no updates) and observe allocated data 
> pages metric grows constantly as expected.
> But the error look too large, used memory (and FillFactor as well) may 2-10+ 
> time differs.
> E.g. allocated pages, fillFactor, usedMem (bytes):(
>  node-0: 13789 0.851563 48096032
>  node-1: 14447 0.781250 46230400
> In next second:
> node-0: 13958 0.039063 2233280
>  node-1: 14624 0.347656 20824576
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to