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] [Updated] (IGNITE-3074) Optimize DHT atomic update future.
Date Wed, 11 May 2016 15:31:12 GMT

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

Vladimir Ozerov updated IGNITE-3074:
------------------------------------
    Fix Version/s:     (was: 1.6)
                   1.7

> 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
>              Labels: performance
>             Fix For: 1.7
>
>
> 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)

Mime
View raw message