Re: [infinispan-dev] moving asyncMarshalling to jgroups
On 19 Jan 2012, at 19:42, Bela Ban wrote:
On 1/19/12 6:36 PM, Galder Zamarreño wrote:
>
>
> On Jan 19, 2012, at 3:43 PM, Bela Ban wrote:
>
>> This may not give you any performance increase:
>>
>> #1 In my experience, serialization is way faster than de-serialization.
>> Unless you're doing something fancy in your serializer
>
> No. I think Mircea didn't explain this very well. What really happens here is
that when asyncMarshalling is turned on (the name is confusing...), async transport
sending is activated. What does this mean?
>
> When the request needs to be passed onto JGroups, this is done in a separate thread,
which indirectly, results in marshalling happening in a different thread.
How is this thread created ? I assume you use a thread pool with a
*bounded* queue.
yes, these[1] are the default initialisation values for the pool.
Returning to the original question, can't we achieve the same functionality (i.e.
marshalling not to happen in caller's thread - that's for async replication
*only*) by passing the marshaller(an adapter) to jgroups which would then serialize it in
the (async) replication thread?
[1]http://bit.ly/zUFIEb