I have a question regaring the performance metrics of putAll vs storing objects directly as List.
which would be more performant 1. store object of the form { key1, {sessionId, List<message>}} 2. store each message object in a list with unique key {key, sessionid, data} and then use putall for storing into geode and then run queriies. in the second case there are going to be innumerable number of records and each object is distinct, but in teh first case it is an arraylist that is getting saved and the query will return List as the result and will have to be decomposed on the client side. In the second case decomposition on client side can be avoided, but there is going to be more work on server side. -- Sent from: http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/