[infinispan-dev] moving asyncMarshalling to jgroups

Bela Ban bban at redhat.com
Thu Jan 19 14:42:10 EST 2012



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. Or are you spawning a new thread on every serialization 
? If that's the case, then you're run out of threads if the 
serialization rate is high...



-- 
Bela Ban
Lead JGroups (http://www.jgroups.org)
JBoss / Red Hat


More information about the infinispan-dev mailing list