ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Lantukh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-2744) Optimize "unwindEvict" call in GridCacheIoManager.processMessage().
Date Thu, 12 May 2016 12:51:12 GMT

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

Ilya Lantukh commented on IGNITE-2744:

2. We couldn't find any place in code where new entry is inserted into that map and assertion
for readMap.isEmpty() never failed. I think it proves that map is never updated.
3. Sure, I will change it.

> Optimize "unwindEvict" call in GridCacheIoManager.processMessage().
> -------------------------------------------------------------------
>                 Key: IGNITE-2744
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2744
>             Project: Ignite
>          Issue Type: Task
>          Components: cache
>    Affects Versions: 1.5.0.final
>            Reporter: Vladimir Ozerov
>            Assignee: Ilya Lantukh
>            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

View raw message