[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=12616456#comment-12616456 ] 

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

Btw, JProfiler snapshots such as the ones in https://issues.jboss.org/browse/JBPAPP-6865?focusedCommentId=12616268&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12616268 look buggy. For a hotrod server put, MVI should be creating two MarshalledValue instances but the profiler shows no calls to MVI.createMarshalledValue(). I've verified this with Michal where he's tried to do a put on a HR endpoint in EDG and he can confirm this.

> 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