You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Kuznetsov (JIRA)" <ji...@apache.org> on 2018/04/26 16:37:00 UTC

[jira] [Comment Edited] (IGNITE-7823) Separate cache for non collocated IgniteSet.

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

Alexey Kuznetsov edited comment on IGNITE-7823 at 4/26/18 4:36 PM:
-------------------------------------------------------------------

LGTM


was (Author: alexey kuznetsov):
LBTM

> Separate cache for non collocated IgniteSet.
> --------------------------------------------
>
>                 Key: IGNITE-7823
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7823
>             Project: Ignite
>          Issue Type: New Feature
>          Components: data structures
>            Reporter: Andrey Kuznetsov
>            Assignee: Pavel Pereslegin
>            Priority: Major
>             Fix For: 2.6
>
>
> Existing collocated version of {{IgniteSet}} datastructure is good enough for small sets.
> For big sets it's too expensive to maintain redundant onheap data copies. Thus it would be better to use separate cache for non collocated {{IgniteSet}} version. The difference between these two kinds of sets should be properly documented afterwards. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)