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/03/17 12:52:33 UTC
[jira] [Comment Edited] (IGNITE-2523) Introduce "single put" NEAR
update request.
[ https://issues.apache.org/jira/browse/IGNITE-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15199377#comment-15199377 ]
Vladimir Ozerov edited comment on IGNITE-2523 at 3/17/16 11:51 AM:
-------------------------------------------------------------------
Moved to 1.7. It looks like we should implement optimized paths for single-updates in futures and only then apply any protocol changes.
was (Author: vozerov):
Moved to 1.7. It looks like we should implement optimzied paths for single-updates in futures and only then apply any protocol changes.
> Introduce "single put" NEAR update request.
> -------------------------------------------
>
> Key: IGNITE-2523
> URL: https://issues.apache.org/jira/browse/IGNITE-2523
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
> Affects Versions: 1.5.0.final
> Reporter: Vladimir Ozerov
> Assignee: Vladimir Ozerov
> Fix For: 1.7
>
>
> Essentially, in this case we could get rid of all collections and garbage inside GridNearAtomicUpdateRequest/GridDhtAtomicUpdateRequest.
> This should drastically decrease message size and improve performance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)