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

Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/03/31 13:43:25 UTC

[jira] [Updated] (IGNITE-2744) Optimize "unwindEvict" call in GridCacheIoManager.processMessage().

     [ https://issues.apache.org/jira/browse/IGNITE-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Ozerov updated IGNITE-2744:
------------------------------------
    Labels: performance  (was: )

> Optimize "unwindEvict" call in GridCacheIoManager.processMessage().
> -------------------------------------------------------------------
>
>                 Key: IGNITE-2744
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2744
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: cache
>    Affects Versions: 1.5.0.final
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>            Priority: Critical
>              Labels: performance
>             Fix For: 1.6
>
>
> We call this method on every (!!!) received cache message. This call is pretty heavy as it iterates over all caches. 
> We need to optimize it. E.g., check evicts only for the cache to which received message belongs. And iterate over the whole set only if we know for sure that several caches are affected (e.g. due to cross-cache TX).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)