Hi Val, Does that mean the on-heap will benefit only when we have more 'get' operations but will degrade the performance with 'put' operations?
Also, why Ignite 2.0 is duplicating data instead of maintaining one copy be in on-heap or off-heap? Would have been helpful, if the Ignite evicted the on-heap entries to off-heap based on eviction policy set by the application. I'll look into Binary Marshaller as well. Thanks -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Enforcing-data-to-be-stored-in-Heap-only-tp15141p15207.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
