Binarylizable is usually used when there is a need for custom serialization
logic, it doesn't affect the performance. It looks like you can go with
default behavior.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Byte-serialization-tp7768p7786.html
between 90k and 300k. What configuration would offer the best
performance for serialization. Right now I am thinking of removing the
Binarylizable interface and just going with default binary serialization.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Byte
y("image", image);
writer.writeUuid("id", id);
writer.writeString("pageFormat", pageFormat);
writer.writeString("documentId", documentId);
writer.writeInt("pageNumber", pageNumber);
}
--
View this message in context:
htt
Hello
One of the objects I am caching has a class member that contains a byte[]
(png image). Are there examples of how to serialize/deserialize this. I am
getting this warning when I look at it in debug mode
WARNING: Class "com.imaging.cache.beans.TiffPage" cannot be serialized
using BinaryMar