[infinispan-issues] [JBoss JIRA] Commented: (ISPN-1267) IsMarshallableInterceptor causes unnecessary marshalling in remote access mode

[Galder Zamarreño (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616454#comment-12616454 ] 

Galder Zamarreño commented on ISPN-1267:
----------------------------------------

More than the isMarshallable implementation, I think it's the fact that MarshalledValue instances are created left and right and these are compacted. MVs are created cos we store wrappers (ByteArrayKey and CacheValue) but the whole storeAsBinary does not make sense in the first place anyway.

So, the solution here is for server startup to disable storeAsBinary/lazyDeserialization. That should apply to HR, Memcached and REST servers too.

> IsMarshallableInterceptor causes unnecessary marshalling in remote access mode
> ------------------------------------------------------------------------------
>
>                 Key: ISPN-1267
>                 URL: https://issues.jboss.org/browse/ISPN-1267
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Marshalling
>    Affects Versions: 5.0.0.CR8
>            Reporter: Michal Linhard
>            Assignee: Galder Zamarreño
>             Fix For: 5.0.0.FINAL
>
>
> this is because by default GenericJBossMarshaller is used and
> GenericJBossMarshaller.isMarshallable implementation marshalls objects to find whether they are marshallable. 
> this proves to be a very significant performance bottleneck, see details in JBPAPP-6865
> in remote access storeAsBinary shouldn't have any performance impact, because the values that are received on serverside are already byte arrays.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira