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<String, BitSet>. 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.
