You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Stanilovsky Evgeny (Jira)" <ji...@apache.org> on 2020/05/28 06:49:00 UTC

[jira] [Created] (IGNITE-13086) Improve current page replacement mechanism.

Stanilovsky Evgeny created IGNITE-13086:
-------------------------------------------

             Summary: Improve current page replacement mechanism.
                 Key: IGNITE-13086
                 URL: https://issues.apache.org/jira/browse/IGNITE-13086
             Project: Ignite
          Issue Type: Improvement
          Components: persistence
    Affects Versions: 2.8.1
            Reporter: Stanilovsky Evgeny
            Assignee: Stanilovsky Evgeny
         Attachments: IgnitePdsPageReplacementTestToYard.java

Experimentally proven that current page replacement functionality has problems with replace candidate computation. Current implementation obtain 5 random pages and make further decisions basing this pages last touch timestamp and some inner flags, however still possible cases when this pages set can be simply nullified due to inner logic. All improvements need to be proven, for example, by simple scenario: 
1. put some data until event EVT_PAGE_REPLACEMENT_STARTED is triggered
2. put 2 times more data than been loaded in p1.
3. execute fullscan (through ScanQuery) for old\cold data processing emulation.
4. start processing only pages which can fit into current mem region.
5. measure "replacedPages" metric.
(i attach code mention above)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)