ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-2264) Optimize GridDistributedTxMapping.
Date Sat, 26 Dec 2015 13:26:49 GMT

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

Vladimir Ozerov commented on IGNITE-2264:

One more major problem - very often there is only one entry in mapping. And we create the
whole LinkedHashSet for it. 
No need for this actually. We can use singleton set or so here.

> Optimize GridDistributedTxMapping.
> ----------------------------------
>                 Key: IGNITE-2264
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2264
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: cache
>    Affects Versions: ignite-1.4
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>            Priority: Critical
>             Fix For: 1.6
> This class has two methods: reads() and writes(). Together they return the whole set
of entries. 
> The problem is that each call creates collection wrapper over entries + 1 additional
iterator per each traverse over collection. This seen as a garbage "hotspot" in flight recorder.
> Actually there is no need for these methods. Instead, we can pass entries collection
directly and filter entries manually.

This message was sent by Atlassian JIRA

View raw message