Prashant, Ignite always stores binary representation of an object. Whenever you read it, its is deserialized which actually creates a copy. In case copyOnRead is set to false, deserialized object if also cached so that deserialization step is skipped. But this doubles memory consumption.
-Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Apache-heap-getting-increase-with-cacheConfig-setCopyOnRead-as-false-tp14175p14184.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
