Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Tue, 25 Oct 2016 15:17:59 +0000 (UTC)
From: "Konstantin Dudkov (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.12963828.1461929907000.79937.1477408679892@Atlassian.JIRA>
In-Reply-To: <JIRA.12963828.1461929907000@Atlassian.JIRA>
References: <JIRA.12963828.1461929907000@Atlassian.JIRA> <JIRA.12963828.1461929907106@arcas>
Subject: [jira] [Assigned] (IGNITE-3074) Optimize DHT atomic update future.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 25 Oct 2016 15:18:01 -0000


     [ https://issues.apache.org/jira/browse/IGNITE-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Dudkov reassigned IGNITE-3074:
-----------------------------------------

    Assignee: Konstantin Dudkov  (was: Alexander Paschenko)

> Optimize DHT atomic update future.
> ----------------------------------
>
>                 Key: IGNITE-3074
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3074
>             Project: Ignite
>          Issue Type: Task
>          Components: cache
>    Affects Versions: 1.5.0.final
>            Reporter: Vladimir Ozerov
>            Assignee: Konstantin Dudkov
>              Labels: performance
>             Fix For: 1.8
>
>
> Current implementation of GridDhtAtomicUpdateFuture is less than optimal. First of all, It allocates lots of collections. 
> We could improve that in several ways:
> 1) Better encapsulate logic around DHT future/request/response, so that collections are not exposed through methods directly.
> 2) Implement specialized version for update with a single key (the most common case).
> Once done, we will be able to easily add single DHT request/response for more efficient IO.


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