You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ivan Rakov (JIRA)" <ji...@apache.org> on 2017/05/11 15:37:04 UTC

[jira] [Commented] (IGNITE-5175) Performance degradation using evictions in near-enabled caches

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

Ivan Rakov commented on IGNITE-5175:
------------------------------------

Current test hang is expected. Entry can't be evicted on local node if it's present in near cache on another node (after some iterations, almost all entries have copies in near cache). Test is changed.

> Performance degradation using evictions in near-enabled caches
> --------------------------------------------------------------
>
>                 Key: IGNITE-5175
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5175
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 2.0
>            Reporter: Igor Seliverstov
>            Assignee: Ivan Rakov
>
> Both RandomLruNearEnabledPageEvictionMultinodeTest.testPageEviction and 
> Random2LruNearEnabledPageEvictionMultinodeTest.testPageEviction fail with timeout exceptions. 
> Seems that the execution time (eviction operation) is non-linearly dependent on a count of elements in the cache (the more elements the longer the operation).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)