You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitriy Pavlov (JIRA)" <ji...@apache.org> on 2018/03/06 12:18:00 UTC
[jira] [Commented] (IGNITE-7638) Page replacement process in PDS
mode affect segment loaded pages table performance
[ https://issues.apache.org/jira/browse/IGNITE-7638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16387685#comment-16387685 ]
Dmitriy Pavlov commented on IGNITE-7638:
----------------------------------------
https://reviews.ignite.apache.org/ignite/review/IGNT-CR-510
https://github.com/apache/ignite/pull/3481
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll&branch_IgniteTests24Java8=pull%2F3481%2Fhead&tab=buildTypeStatusDiv
> Page replacement process in PDS mode affect segment loaded pages table performance
> ----------------------------------------------------------------------------------
>
> Key: IGNITE-7638
> URL: https://issues.apache.org/jira/browse/IGNITE-7638
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Reporter: Dmitriy Pavlov
> Assignee: Dmitriy Pavlov
> Priority: Critical
> Fix For: 2.5
>
>
> There is
> - durable memory segment in PDS enabled data region
> - page replacement started
> then Ignite performance slow down occurs, JFR & Visual VM shows get&put from FullPageIdTable requires significiant time to be executed (~5-10% оf samples count and up to 40% CPU usage)
> {noformat}
> Avg steps in loaded pages table, get: 9456 steps, put: 20243 steps, capacity: 20242 size: 7978
> {noformat}
> Effect of influence of FullPageID table is cumulative, once it starts to grow, number of steps required grows also.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)