ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Lantukh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-2523) Introduce "single put" NEAR update request.
Date Mon, 29 Feb 2016 14:18:18 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171903#comment-15171903
] 

Ilya Lantukh commented on IGNITE-2523:
--------------------------------------

I wrote tests, but they fail for clock mode - in this case GridNearAtomicUpdateFuture uses
fast map logic and our new code for version selection is not executed.
This case should be meticulously investigated and changed to generate optimized requests for
single-entry updates.

> 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: Ilya Lantukh
>             Fix For: 1.6
>
>
> 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)

Mime
View raw message