[jbosscache-issues] [JBoss JIRA] Commented: (JBCACHE-1419) If async repl is used, marshalling should be done in a separate thread

[Manik Surtani (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBCACHE-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12431956#action_12431956 ] 

Manik Surtani commented on JBCACHE-1419:
----------------------------------------

Benching would be interesting after this optimisation - I expect a 20% performance improvement in async replication since about that much time is taken in marshalling.

This may involve a new config parameter for the size of the async replication bounded queue, and perhaps warrants some refactoring with the replication queue code since there is stuff that could be reused.

> If async repl is used, marshalling should be done in a separate thread
> ----------------------------------------------------------------------
>
>                 Key: JBCACHE-1419
>                 URL: https://jira.jboss.org/jira/browse/JBCACHE-1419
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Replication
>            Reporter: Manik Surtani
>            Assignee: Manik Surtani
>             Fix For: 3.1.0
>
>
> We need to be aware of classloaders though - perhaps the use of  a Future containing a ReplicationUnit, which contains the Command as well as the associated thread context classloader.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira