Hi Shawn,
BitSet will be marshaled using BitSet.writeObject() serialization
implementation. In other words, if this approach saves your memory in heap,
it will save it in Ignite as well.
If you save collection of strings, Ignite will not check for duplicates as
JVM does, and as mentioned Alexey,
not save
> so much memory?
>
>
>
> If there any tips to save memory for above case. Thanks in advance.
>
>
>
> Thanks
>
> Shawn
>
>
>
> *发件人:* shawn.du [mailto:shawn...@neulion.com.cn]
> *发送时间:* 2017年1月3日 18:37
> *收件人:* user@ignite.apache.org
> *抄送:
37
收件人: user@ignite.apache.org
抄送: user@ignite.apache.org
主题: 回复：BinaryObject and String.intern
thanks <mailto:dkarachent...@gridgain.com> dkarachentsev.
在2017年01月03日 18:25， <mailto:dkarachent...@gridgain.com> dkarachentsev 写道:
Actually no, because Ignite internally will store it
thanks dkarachentsev.
在2017年01月03日 18:25，dkarachentsev 写道:Actually no, because Ignite internally will store it as a BinaryObject and
will send to other nodes in a binary format as well, where all string fields
will be unmarshaled without intern().
--
View this
