ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Dudkov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-2523) Introduce "single put" NEAR update request.
Date Mon, 07 Nov 2016 13:03:58 GMT

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

Konstantin Dudkov commented on IGNITE-2523:


I've added size() and key(int idx) methods (trying to keep naming principles same as in Dht
requests). In that case I don't think it's possible to remove keys() method: sometimes collection
from this method is passed to other objects so refactoring would be too massive. I've also
added singleton keys collection inside single request class to get rid of creation collection
for each call.

Please take a look and give me feedback.

> Introduce "single put" NEAR update request.
> -------------------------------------------
>                 Key: IGNITE-2523
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2523
>             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
> 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

View raw message