Hi, Ignite stores your classes in binary format, which is very compact, so these changes should not change much from memory consumption standpoint. I would recommend to use types that fit particular fields better from business case standpoint (e.g., long for account number, Date for birthday, int for postcode, etc.).
Also I would not recommend to use strings as keys if that's possible. String's equals method has to do one-by-one char comparison, which is obviously much slower that comparison of two longs. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Optimizing-data-model-to-be-stored-in-data-grid-with-less-cache-size-tp2977p2987.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
