[infinispan-dev] performance issue when using return types
Manik Surtani
manik at jboss.org
Mon Nov 21 17:26:08 EST 2011
On 21 Nov 2011, at 18:01, Mircea Markus wrote:
> Hi,
>
> The DistributionInterceptor can be simplified significantly now that we are supporting transactional or non transactional caches.
> Looking at it I've found an significant performance issues though: seems like for each put we do, if the unreliableReturnValues is disabled (that's the default, i.e. disabled) then we do a remote get and then a put, i.e. 2 RPCs to the same remote node. That seems to be highly inefficient so just wondering is there any reason not to piggyback the return value on the put itself?
Agreed, but this will involve separate PutKeyValueCommands for replicated vs. distributed mode. Unless you pass in a flag to the command.
--
Manik Surtani
manik at jboss.org
twitter.com/maniksurtani
Lead, Infinispan
http://www.infinispan.org
More information about the infinispan-dev
mailing list