I recently had a very bad experience with Kryo. A JGroups user used Kryo
to marshal data types into byte buffers which he then broadcast around
using JGroups (details in [1]).
Turns out the culprit was Kryo temporarily flipping bits in an already
marshalled buffer passed to JGroups. Of course r
On 31/01/14 13:35, Radim Vansa wrote:
> Worth to note that Infinispan does not have true async operation -
> executing synchronous request in another threadpool is rather simplistic
> solution that has serious drawbacks (I can imagine a situation where I'd
> do 100 async gets in parallel, but thi
At the JGroups level, ASYNC generates *less* traffic than SYNC. So if
you do sync under the cover and use a future to make it async at the API
level, you're incurring more overhead, namely the messages sending back
the responses.
Not sure about the Infinispan async API, but I'd assume this woul
