Re: binary output from cache

2017-02-10 Thread ALEKSEY KUZNETSOV
thanks for explanation пт, 10 Фев 2017 г., 20:12 Alexey Goncharuk : > Aleksey, > > It can give a performance benefit for example if you access only a subset > of the fields of a large object. In this case, deserializing only required > fields is much faster than

Re: binary output from cache

2017-02-10 Thread Alexey Goncharuk
Aleksey, It can give a performance benefit for example if you access only a subset of the fields of a large object. In this case, deserializing only required fields is much faster than deserializing the whole object. --AG 2017-02-10 10:26 GMT+03:00 ALEKSEY KUZNETSOV :

Re: binary output from cache

2017-02-09 Thread ALEKSEY KUZNETSOV
How could it give perfomance improvement ? чт, 9 февр. 2017 г. в 23:21, Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Alexey, > > Generally users want to work with their model objects, so we deserialize > them on read by default. BinaryObject API is usually used in more > complicated

Re: binary output from cache

2017-02-09 Thread Valentin Kulichenko
Alexey, Generally users want to work with their model objects, so we deserialize them on read by default. BinaryObject API is usually used in more complicated use cases, like when values are read on servers side, or when it gives performance improvement. -Val On Thu, Feb 9, 2017 at 10:36 AM,

binary output from cache

2017-02-09 Thread ALEKSEY KUZNETSOV
Guys, i have a dumb question. Why do we need to set withKeepBinary()? What i mean is why dont we just have it hardcoded ? -- *Best Regards,* *Kuznetsov Aleksey*