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-2566) Get rid of MiniFutures in GridDhtTxPrepareFuture
Date Tue, 09 Feb 2016 15:07:18 GMT

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

Ilya Lantukh commented on IGNITE-2566:
--------------------------------------

Similar to https://issues.apache.org/jira/browse/IGNITE-2533, there is no significant performance
increase.

> 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
>             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)

Mime
View raw message