[infinispan-dev] putAll, getAll and optimization fruits

>> getAll and putAll and nothing more than a glorified sequential call to get / put in a for loop. >> The execution of gets and puts in parallel for it costs o(n) network trip in latency rather than o(1). >> How could we improve it ? > Historically getall and putall were not intended as hotrod operations and were actually implemented only to honor the map interface. > The most we can do RPC wise to optimize these operations is to group all keys mapping to the same server node into a single request. That would reduce the number of RPCs, but in big O talk it would still be O(numKeys). Executing them in parallel sounds like a good idea to me. Curious to hear other thoughts on this. Galder? So there are actually three improvements: * getall and putall as hotrod operations (no matter how that will be implemented by the server itself) Galder, is it possible in current HR design to execute requests in parallel, without consuming one thread for each node? That was something my async client should solve, but afaik it's not possible without substantial changes, and we were rather targetting that for future JDK 8 only client.

Anyway, we could route the HR request to the node with most matching keys.