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/04/29 13:39:13 UTC

[jira] [Created] (IGNITE-3074) Optimize DHT atomic update future.

Vladimir Ozerov created IGNITE-3074:
---------------------------------------

             Summary: 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: Vladimir Ozerov
             Fix For: 1.6


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)