[jira] [Commented] (IGNITE-3813) High contention on GridCacheMapEntry.obsolete() on loading data to data stremer with composite keys

["Taras Ledkov (JIRA)" <ji...@apache.org>]

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

Taras Ledkov commented on IGNITE-3813:
--------------------------------------

At the stacktrace I see a possible contention at {{CacheObjectBinaryProcessorImpl.affinityKey}} and then on the metadata of binary marshaler. Because the method {{CacheMapEntry.obsolete}} is synchronized.


> High contention on GridCacheMapEntry.obsolete() on loading data to data stremer with composite keys
> ---------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-3813
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3813
>             Project: Ignite
>          Issue Type: Improvement
>    Affects Versions: 1.7
>            Reporter: Dmitry Karachentsev
>            Assignee: Taras Ledkov
>             Fix For: 1.8
>
>         Attachments: jstack.log
>
>
> On loading entries with non-primitive key to data streamer too many calls to metadata cache which causes high contention on GridCacheMapEntry.
> Example thread dump in attachment.



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