Re: 答复: 回复：BinaryObject and String.intern

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,

回复：BinaryObject and String.intern

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

Re: 答复: BinaryObject and String.intern

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 message in context:

答复: BinaryObject and String.intern

If I don't use binary object and use POJO and never call keepBinary, it will? Thanks Shawn -邮件原件- 发件人: dkarachentsev [mailto:dkarachent...@gridgain.com] 发送时间: 2017年1月3日 15:16 收件人: user@ignite.apache.org 主题: Re: BinaryObject and String.intern This won't give you any benefit, because

Re: BinaryObject and String.intern

This won't give you any benefit, because Strings will be marshaled and stored in binary format. In other words you'll get a binary copy of your string, which is managed just like any other object. -- View this message in context:

BinaryObject and String.intern

Hi experts, I am trying to use String.intern to save memory, below is Pseudo code, will it work? public class Example { String[] values; } Map fields = new HashMap(); fields.put("example",Example.class.getTypeName());