[
https://issues.apache.org/jira/browse/IGNITE-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666463#comment-15666463
]
Konstantin Dudkov commented on IGNITE-3074:
-------------------------------------------
pr https://github.com/apache/ignite/pull/1232
tests:
http://ci.ignite.apache.org/project.html?projectId=IgniteTests&tab=projectOverview&branch_IgniteTests=pull%2F1232%2Fhead
> 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)
