[ https://issues.jboss.org/browse/JGRP-1989?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on JGRP-1989: --------------------------------------- {quote}I don't agree that most of the messages are large (or that the size is predictable at all). In Infinispan, we send a lot of small messages, e.g. a remote get command only contains a small key, or the response might be just a few bytes to indicate the operation is successful. {quote} In many practical use cases, even if I do many get operations the keys will be of some known type; let's even assume they are {{String}} instances, one might know that they are of some lengths in the ballpark 2 bytes to 15 bytes (for example, but I think that's a reasonable use case). In this scenario, one would make a large pool and split them in stripes of 15 bytes each. That would "overallocate" frequently but being out of heap memory, it's a cheap but convenient trick. I simply don't believe that applications are truly "schema-less": even if there's not an upfront declared schema, any app will have a soft schema at least which means there are patterns in data access. Of course it would not be very efficient to mix access to different types in the same cache, but that's not something we encourage either (especially considering a Cache is a generic with K,V to be defined as types). bq. we send *a lot *of small messages So this proposal would have *a lot *of benefits ;) -- This message was sent by Atlassian JIRA (v6.4.11#64026)