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:46:25 UTC

[jira] [Commented] (IGNITE-2566) Get rid of MiniFutures in GridDhtTxPrepareFuture

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

Vladimir Ozerov commented on IGNITE-2566:
-----------------------------------------

Ilya, let's close the ticket then.

> Get rid of MiniFutures in GridDhtTxPrepareFuture
> ------------------------------------------------
>
>                 Key: IGNITE-2566
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2566
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: general
>            Reporter: Ilya Lantukh
>            Assignee: Ilya Lantukh
>              Labels: performance
>             Fix For: 1.6
>
>
> GridDhtTxPrepareFuture is instantiated for every transaction. In uses compound future + minifutures concept, which is an overhead for it's rather simple logic.
> It should be refactored to store miniId to request mapping internally and update it's state on every response without generating additional objects.



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