Performance benefit of using withKeepBinary when getting the whole object on client side

[hitendrapratap <hi...@target.com>]

Will be there any performance benefit between the below if we execute these
statements from client and getting the whole CustomObject on client side:

1. Executing on client side with KeepBinary
IgniteCache<Integer, BinaryObject> cache = igniteInstance.cache("cache")
                    .withKeepBinary();
BinaryObject value = cache.get(1);
CustomObject object = <CustomObject>value;


2. Executing on client side without KeepBinary
IgniteCache<Integer, CustomObject> cache = igniteInstance.cache("cache");
CustomObject object = cache.get(1);



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Performance-benefit-of-using-withKeepBinary-when-getting-the-whole-object-on-client-side-tp10389.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Performance benefit of using withKeepBinary when getting the whole object on client side

[vkulichenko <va...@gmail.com>]

BinaryObject is binary representation of the object, so you avoid
deserialization step. This can be useful if you don't have a class
definition on the node where you do get(), or if you don't need the whole
object (e.g., only one field value out of many).

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Performance-benefit-of-using-withKeepBinary-when-getting-the-whole-object-on-client-side-tp10389p10404.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.