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

2017-01-04 Thread dkarachentsev 
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, there is still no compression supported.
So only you can do is to write algorithms in your side to handle such cases
like your Map.

Thanks!



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/BinaryObject-and-String-intern-tp9826p9891.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

回复：BinaryObject and String.intern

2017-01-03 Thread shawn.du 


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 message in context: http://apache-ignite-users.70518.x6.nabble.com/BinaryObject-and-String-intern-tp9826p9834.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.